Native & Search API enables you to programmatically buy, manage and optimize mobile search and native advertising for campaigns across Oath’s mobile inventory.
The Native & Search development and support teams have collected these best practices in an effort to provide you with strategies for optimizing your work with the Native & Search API and achieving best results for your mobile and native ad campaigns.
Best practices are grouped into the following categories:
|Pre-live||Tips to follow before you go live, like verifying your overall budget, checking for
|Once-live||Tips after you go live, like using compressed files for bulk operations, using the books closed (COB) endpoint and using the Audience cube report to get device information for native ads.|
|Dot Tags & Custom Audience||Some best practices for dealing with dot tags and custom audiences, like using a single tag/pixel per account and placing the Dot tag only once on a webpage.|
Before going live, follow these best practices:
- Verify your overall budget as well as your allocation (daily vs. lifetime) using https://api.gemini.yahoo.com/v2/rest/campaign/?advertiserId=12345678
- Check that the destination URL in use is correct.
- Perform an ad preview across devices via https://api.admanager.yahoo.com/v1/rest/preview. To get a preview for an existing ad id and deviceType=handheld: https://api.gemini.yahoo.com/v2/rest/preview/?adId=31027685344&displayType=handheld
- Check for
imageUrlHQis not required, not having it will impact both performance and delivery. Many native placements (including homepage and almost all of mobile) require it.
- The recommended Daily Frequency Cap for App Install is 2; the weekly cap is 4.
- Mention the Brand name in the title.
- Try to limit native video ads to 15 seconds, as they drive greater recall and purchase intent than longer video units.
- Allow enough time for testing and optimization. Start with 2-4 weeks worth of budget.
Once you are live, follow these best practices:
- Use the Audience cube report to get the device information (Mobile vs. Other) for Native ads.
- Always use the books closed (COB) endpoint and run reports only after it returns true. This ensures that the data is certified and final.
- Run the COB endpoint call around 4 AM of the advertiser’s time zone.
- For faster reports, use fewer metadata fields.
- For performing A/B tests of ad copies, create one test ad per ad group.
- Use compressed files for bulk operations.
- Use the API if you’re updating < 500 objects; otherwise, use Bulk.
- Use Bulk for larger, less frequent uploads and downloads.
- Always use compressed files for bulk operations (upload limit = 1 GB).
- On re-try polling of reports, it’s recommended that you wait for 5 minutes and retry again at 1 minute intervals. For small reports that usually return in 5 minutes, abandon the job id after 30 minutes. For longer reports abandon after 2 hours.
You may wish to check out these other resources dedicated to working with Native & Search Platforms and the Native & Search API: