If you're using the Connected Web feed format, just follow the specification of the Advertising body element. We currently don't support targets and semantic_hide parameters.

If you're using an RSS or Atom feed, you must include your ads using an image tag and setting its role parameter equal to advertising, as shown in the following example: <img src="https://fbwcdn.com/image/ads/example_add.jpg" role="advertising"/>
Then wrap your ad-image tag with an a tag and set its href parameter to the web page that the add must show, its role parameter equal to advertising and its type parameter equal to one of the supported ads type (see here for more):
<a href="https://flashbeing.com/new_offer/" role="advertising" target="_blank"><img src="https://fbwcdn.com/image/ads/example_add.jpg" role="advertising"/></a>

If the user is using a FlashBeing's app, the link will be opened using the embedded in-app browser, else it will be opened in a new tab of the browser.

When an user interacts with a content, for example when he/she saves it for later, a persistent copy of the content will be created. This means that if you update on future contents the ads links and banners, changes wont be applyed. To avoid this, you can use dynamic links which will remain the same on contents but will rdirect to a different location and include a different image banner when new ads are available.

For istance, if the link to your add is https://mywebsite.com/ads/one/, you can include in your content the following link https://mywebsite.com/ads/current/ which will automatically rdirect to https://mywebsite.com/ads/one/.
You can do the same with images: https://mywebsite.com/ads/current/banner/ which will rdirect to https://mywebsite.com/ads/one/banner.jpg.

We currently do not share any kind of information about the user who's requesting a content, for this reason currently profiling can ony be defined using:

• the topic of your website
• the kind of topics which matters for your users