What's an embargo? 

When your release is available under embargo it means that it is only available through a secret link. When you visit your release through this link, there is a clear banner explaining your release is under embargo and that it will be published on the date you've chosen. This comes in handy if you'd like to give journalists time to work on their story or when you want to give certain contacts early access. Once your release gets published the secret link will simply redirect to the public link.

Yes, you can absolutely send out embargoed releases with pr.co. It works the same as how you would usually send out an article or release; however this time you'll schedule your emails to go out before the release is published. 

So, your workflow is as follows: 

1. Write your release
Just write your release as you would typically do.

2. Add your campaign's publishing details
Schedule your release for the time you want the release to be publicly available to everyone.  

3. Add the emails prior to your release
Write the emails, and set the distribution date to the date and time on which you want the embargoed release to be sent out. So, the distribution date must be a date prior to the publish date. 

4. Confirm the campaign
Once the release is confirmed, the emails with the embargoed release will go out at the selected time. When the recipients click on the link in the email, they'll be able to read the release, but there will be a massive red banner on the top of the release that states: "UNDER EMBARGO. DO NOT PUBLISH BEFORE: [publish date]"

Once you have gone through the steps above, you are able to retrieve the secret link to your embargoed campaign if you wish to share the link with other contacts or preview it. You can access it by clicking on the title of your campaign, which will lead you to a page where you can find the secret link in the "Private link (embargo)" section:

And that's it! 

If you have any more questions ❓or feedback 💬, contact our support team. We'd love to hear from you 💌

Did this answer your question?