The platform associated with an ad affects a number of things, this article explains how
We covered why the Platform associated with an ad is critical when publishing your ad elsewhere, this article explains the impact Platform has on building and serving your ad.
Ad Building
This article explains how most of the Rules available in Studio work - but there are a number of other Rules that aren't mentioned because they are only available when the ad is being served across certain publishers. For example, personalising an ad according to Podcast Name or Genre is only possible when the ad is being served into podcasts.
For this reason, Studio makes it impossible to use a Rule that relies on data that is only available on a specific Platform unless that Platform has been selected.
Ad Serving
Selecting Platform is important for two reasons in the context of ad serving.
The format of our response
In the majority of cases, Platforms require the A Million Ads Platform to provide ads in a VAST format but sometimes Platforms have more custom requirements. Selecting a Platform in Studio drives the format in which the A Million Ads Platform will provide the ad.
Processing data passed to us by the Platform
Sometimes an ad is relying on data (e.g. Podcast Name, Audience, Zip Code etc.) being passed into the A Million Ads Platform on the ad request. In this case, it is critical that the tag that Studio produces is formatted exactly as it should be.
In the below example:
- abc123 is the identifier for the ad in the A Million Ads Platform
- BestDSP is the identifier for the platform in the A Million Ads Platform
- zip is the label that the A Million Ads Platform uses to process user's Zip Codes
- %%zip_code%% will be substituted with the user's Zip Code by Best DSP when they send the ad request to the A Million Ads Platform (known as a macro)