How To: Activate a Sponsored Post


The Tempest Sponsorship Post product includes several properties available through the "Activate Sponsorship" prompt in the Tempest Composer. 

For details on the product, visit the Sponsorship Post guide. To inquire about sponsorship opportunities, reach out to the Tempest Solutions team.


Below are instructions on how to add values and images to the "Sponsored" section on Tempest detail pages (articles, recipes, and organizations). 

Sponsored Content includes the following components which must be set up in the CMS in the "Sponsored" section of the composer:

  • A badge which identifies the brand logo behind the content, displayed at the top of the content. Badge may include a click-to-site. (Badge 1)
  • A second badge (can be the same asset or a different one) optionally supported at the bottom of the content. Supports a click-to-site, which may be different than the first one. (Badge 2)
  • A unique id, which can be used for precise page view tracking as well as ad targeting. This is called the Sponsorship ID in the composer.
  • Third party page view tracking pixels are supported if needed.
  • Links within sponsored content should be marked as "nofollow" to avoid paid-link SEO penalties.

In addition to the above components there is a checkbox labelled "Activate Sponsorship." When selected, Sponsored Content layout is applied to the content. It also triggers the Sponsorship to be set live. If this field is left unchecked the Page Template will not be changed and the sponsorship will not be activated.

Step 1: Check 'Activate Sponsorship' in CMS

Scroll to the bottom of the article, expand "Sponsored" section, and click "Activate Sponsorship."


Step 2: Place the Sponsorship ID

For Say-sold Accountable Content campaigns, the Salesforce Opportunity Line Item ID is associated with the content as the Sponsorship ID. Tempest publishers may use any value that they choose, or omit the value entirely.

If this is a sponsorship the publisher has sold directly use a unique naming convention here i.e. JOKPOST1Winn

The ID used here can also be used for ad targeting, since it is passed to the ad server as the "Sponsorship Line Item ID" key value. Targeting the ID is an easy way to target ads to the sponsored post.

Step 3: Pageview Pixels

Place any client provided 3rd party tracking or view  pixel as URL portion only, i.e.

Step 4: Badge

Upload the logo badge if applicable (Say produced if Say Sold)

Image width for the uploaded asset must be at least 100px wide and at most 1000px wide. Image height for the uploaded asset must be at least 100px tall and at most 160px tall. The image will be displayed half of the width and height of the uploaded asset to support retina displays.

Step 5: URL

Enter the Click thru URL for the logo badge and sponsorship branding. Note: if Say sold this is commonly a bitly of the client provided tracking URLs

Step 6: "No Follow" Links

Google recommends that paid links include the "rel=nofollow" attribute, which lets their crawlers know that the links should not be considered as part of overall PageRank. Any links within Sponsored Content can be considered paid links, and should have the "nofollow" attribute set. Highlight the link in the composer and click the "link" icon to open the edit box where you can check the "No Follow" button.


Labels (programmed in Site Config)

When a sponsorship is applied to a piece of content the section label is automatically changed to read "Sponsored Story" by default. The goal of this label is to clearly call out that the piece of content is sponsored on hub pages. 

This "Sponsored Story" label copy can be changed via the Site Config. Under the group "Branded Content" there is a field called "Card Disclosure Caption." The copy that you include in that field will be used as the copy for the Sponsored Content label on hub pages. Note that when changing this copy the Site Config should be "Updated." It may take a few minutes to reflect the change on the live site.





Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk