{"id":1306,"date":"2021-01-07T17:14:44","date_gmt":"2021-01-07T17:14:44","guid":{"rendered":"https:\/\/wiki.pontiac.media\/?page_id=1306"},"modified":"2022-04-11T15:53:37","modified_gmt":"2022-04-11T15:53:37","slug":"improving-pacing","status":"publish","type":"docs","link":"https:\/\/wiki.pontiac.media\/?docs=new-test-section\/troubleshooting-improving-performance\/improving-pacing","title":{"rendered":"Improving Pacing"},"content":{"rendered":"\n

If you are unsatisfied with the scale of your campaign or your Line Items are pacing below 80%, we recommend evaluating the following potential issues or obstacles to delivery and making changes to your campaign accordingly. <\/span><\/p>\n\n\n\n

  1. Dynamic Budget Multiplier<\/strong>
    Applying the Dynamic Budget Multiplier to your Line will allow the Pontiac Platform to adjust daily budgets to catch up the pacing. To turn on the Dynamic Budget Multiplier, open the Line item, select ‘Edit’, check the ‘Allow Dynamic Budget Multiplier’ box and submit changes.<\/li>
  2. Dynamic Frequency<\/strong>
    Applying Dynamic Frequency to your Line will allow the Pontiac Platform to increase or decrease the daily and lifetime frequency caps based on pacing. If your Line is pacing behind, this feature will increase the frequency that each user can see your ad allowing the Line to increase delivery. To turn on Dynamic Frequency, open the Line item, select ‘Edit’, check the ‘Allow Dynamic Frequency’ box and submit changes.<\/li>
  3. Increase Bids
    <\/b>Higher bids will help win more impressions and will also improve the quality of the inventory.\u00a0If you are targeting an Onboarded Audience or a Third-Party Audience with an additional cost, we<\/span> recommend that you add the associated price of the most expensive segment to your base and max bids to ensure that you can win impressions. The closing CPM will include the cost of the Audience data, so if your base bid is $2.43 and you\u2019re targeting an Audience with a cost of $2.00, you would really be bidding $0.43 for the media. See our general bid recommendations here: Bid Recommendations<\/span><\/a>.<\/span><\/li>
  4. Remarketing Audience size
    <\/b>If this is a remarketing campaign, the size of the audience may be restricting delivery. It takes some time after the pixel is placed on the website to build a substantial remarketing Audience. If the remarketing pixel was recently placed, it is normal for delivery to be limited and additional changes do not need to be made at this time. To check the loads for a Remarketing segment open the Advertiser menu and expand the Audience section to view the Audience metrics. You should see \u2018Total Loads\u2019, \u2018Avg Daily Uniques\u2019, and \u2018Avg Monthly Uniques\u2019. If your Remarketing segment is showing 0 \u2018Loads\u2019 after it has been placed for several days, there may be an issue with the pixel placement. Reach out through the Help Center for assistance in checking pixel placement.
    You can increase your remarketing segment size by launching a simultaneous prospecting campaign, driving new users to your website who will then be added to this Audience. Additionally, you can add the segment pixel into the Creatives of your prospecting campaign to further increase your audience size by also adding users into the pool who see your ads, but don\u2019t click on them or land on your website.<\/span><\/li>
  5. Third-Party Audience Loads
    <\/b>If you are using Third-Party Audiences reach out through the Help Center to check the metrics for these Audiences. If the Audience does not contain an adequate number of users, your Account Manager can recommend similar Audiences with more users that should improve delivery.<\/span><\/li>
  6. Custom or On Boarded Audience Size
    <\/b>Appropriate targeting will help make your campaign stronger. However, keep in mind, if the targeted pool is too small, the scale of your campaign will be limited. It is important to strike a balance between targeting and Audience size.<\/span><\/li>
  7. Multiple Audience Segments
    <\/b>If you are using several audience segments, open the Line Item menu and look at the green box\/boxes that contain the Audiences you are targeting. If there is an \u2018And\u2019 between the segments or groups of segments, this is restricting delivery to ONLY serve to individuals who belong to ALL of these segments or groups of segments. Layering several Audiences in this manner could severely restrict the size of your potential Audience and will limit impressions served. You can edit the logic by editing the Line and selecting \u2018Associate Segments\u2019. This will open the Audiences window where you can modify targeting to \u2018Any\u2019 or \u2018All\u2019 between segment groups.\u00a0For more information see here:     Boolean Logic<\/span><\/a>.<\/span><\/li>
  8. Geo Targeting
    <\/b>Geo-targeting is a valuable strategy to reach your desired Audience, however, if the geographic area that you are targeting is too small, delivery of your campaign could be restricted.\u00a0If you are using zip codes, try using the \u2018Expand Zip Targets\u2019 feature. By adding additional zip codes within a tight radius you may achieve better scale and still stay in the target area. In the Targeting menu, open the zip code tab. Enter a radius in meters and select \u2018Get Zips\u2019. This will find zip codes within this radius from the center point of the zip code\/s entered. A window will open showing you the list of zip codes found within this radius. Select \u2018Add Zips\u2019 to add the new zip codes to the targeting on the Line Item. If you are using a Lat Long Audience try expanding the Radius from 150m to 2251m. This should expand the potential Audience size and increase delivery.<\/span><\/li>
  9. Site lists\/App lists
    <\/strong>It is possible that the sites or apps that you are targeting do not have ads on them, have limited traffic, the ad slots are not available through the open exchange or the available ad sizes differ from the sizes you are using. As a general rule of thumb you can enter the site domain into your browser followed by ‘\/ads.txt’\u00a0 to see a page detailing sellers through which ads on this domain can be purchased. For example, <\/span>    www.yahoo.com\/ads.txt<\/span><\/a>. If you see \u2018appnexus.com\u2019 followed by RESELLER, on this list, then the site may be accessible through Pontiac. This does not guarantee that you will be able to serve on this site, that the ad sizes you are trying to use match the available slots on the site, nor that you will win the auctions for this site. The only way to know for sure if you can access these sites or apps is by testing it. You can try incremental increases in the bids to see at what CPM these sites might clear or expanding your site list with similar sites.\u00a0 If you are not achieving the desired scale, but would like to target contextually a custom contextual segment could be a good alternative. Read more on this option here: Custom Contextual Targeting<\/span><\/a><\/span><\/li>
  10. Sensitive Creatives
    <\/b>If one of your Creatives is flagged as \u2018Sensitive\u2019, this content is allowed on the platform, but <\/span>the Line Item will be restricted to the sensitive publishers that allow this type of content.<\/b> Any exchanges that you selected to target will be \u2018grayed\u2019 out and only the exchanges allowing sensitive content will be targeted. <\/span>This may restrict both delivery and performance of your campaign as these exchanges typically contain lower quality inventory and can also include fraud. <\/b>Audit results can only be changed by resolving the issue that caused the Creative to be flagged as sensitive. If you think your Creative was flagged incorrectly, reach out through the Help Center.\u00a0<\/span><\/li>
  11. It is important to strike a balance between targeting and scale.\u00a0<\/strong>If you are utilizing multiple targeting parameters on the same Line (Geo targets, Audience data, Site\/App lists etc) you may be ‘over-targeting’ and restricting the Line from serving. Try removing or expanding one or more of the targeting parameters to see if the Line begins to serve.<\/li><\/ol>\n","protected":false},"author":1,"featured_media":0,"parent":597,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-1306","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/1306","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1306"}],"version-history":[{"count":2,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/1306\/revisions"}],"predecessor-version":[{"id":7622,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/1306\/revisions\/7622"}],"up":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/597"}],"next":[{"title":"Uneven Delivery","link":"https:\/\/wiki.pontiac.media\/?docs=new-test-section\/troubleshooting-improving-performance\/uneven-delivery","href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/7613"}],"prev":[{"title":"Improving Campaign Performance","link":"https:\/\/wiki.pontiac.media\/?docs=new-test-section\/troubleshooting-improving-performance\/improving-ctr-or-cpa","href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/1310"}],"wp:attachment":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1306"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fdoc_tag&post=1306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}