Frequently Asked Questions (FAQ)

Yes, but your client needs to give you write permissions to their Campaign Manager 360 account so you can make changes to the campaign setup.

These are the permissions your user role needs to re-fetch delivery data:

• DDM reporting UI access Source permission
• Enable Verification Source permission
• Modify all saved reports
• View all generated files
• View all saved reports Source permission
• View audience report
• View click-through conversions Source permission
• View cost Source permission
• View cross-device conversions
• View cross-dimension reach report
• View custom Floodlight variables data
• View Floodlight impressions and unattributed conversions Source permission
• View path to conversion reports
• View revenue data Source permission
• View time lag to conversion report

If your profile has these permissions but you still can't export, it's possible your Campaign Manager 360 admin restricted them for a specific campaign or advertiser.

The minimum permissions you need to export from Basis are:

• Advertiser management: Modify access
• Campaigns: Full access
• Placement costs: Full access
• Placements: Full access
• Sites: Full access

Reach out to your Campaign Manager 360 admin for assistance.

See Tracking Landing Page View Events with Google Tag Manager.

This guide teaches you how to track Landing Page View (LPV) with Universal Pixels in Google Tag Manager (GTM).

See Tracking Button Click Events with Google Tag Manager.

This guide teaches you how to track Button Click Events with Universal Pixels in Google Tag Manager (GTM).

See Tracking Button Click Events and Piggybacking into Campaign Manager 360’s Floodlight.

This guide teaches you how to track Button Click events with piggybacked Universal Pixels in existing Campaign Manager 360 Floodlights.

See Tracking Form Fill Events with Google Tag Manager.

This guide teaches you how to track Form Fill Events with Universal Pixels in Google Tag Manager (GTM).

See Tracking iframe Events with Google Tag Manager.

This guide teaches you how to track iframe Events with Universal Pixels in Google Tag Manager (GTM).

Yes, bid shading works with PMP deals.

Yes, bid shading works with algorithmic optimization (AO), machine learning optimization (MLO), and group budget optimization (GBO).

Optimizations apply independently and sequentially. Bid shading occurs during the bid, aiming to decrease the bid price without changing what the tactic is optimizing towards. This keeps the probability of winning the auction high enough to not compromise pacing and target budgets.

If you have manual optimizations on domains and placements, the manual bid price applies first, and then bid shading takes effect.

Yes, bid shading works with bid multipliers to adjust the final bid price.

There is no minimum CPM required to use bid shading.

We recommend buffering ad serving fees because tactics that use bid shading could see an increase in impressions. Bid shading makes the CPM more efficient, which delivers more impressions, and this would increase ad serving fees and impact pricing.

The option for enabling cookieless conversions is available for creatives and universal pixels. Cookieless conversions are enabled by default for all new ads and universal pixels that you create. For existing ads and pixels, you must select this option manually.

Note that cookieless conversion attribution is only available for universal pixels, not audience or conversion pixels. Make sure that the universal pixel is deployed on at least the landing and conversion pages of the advertiser site.

No. The DSP considers all available information when attempting to attribute a conversion. If the user has a cookie ID, that is considered for performing conversion attribution in addition to any information from cookieless conversion attribution. If cookieless conversion cannot work for some reason, attribution will continue using cookie IDs wherever possible.

Cookieless conversion supplements existing conversion attribution. It will never reduce the number of conversions counted.

No. Cookieless conversion attribution is only compatible with universal pixels, not audience or conversion pixels.

No, bulk editing to enable cookieless conversions is not yet available.

No, you only need to use a single universal pixel on your webpages. As long as it has cookieless conversion enabled, a universal pixel will cover both standard cookie-based conversion attribution and cookieless conversions.

In general, no. Enabling cookieless conversion for your universal pixels will only improve your ability to measure conversions in all environments.

Some advertisers might have a business policy to not permit marketing tags on their site to write to localStorage. In that case, you can turn cookieless conversion off for the universal pixel by clearing the Enable cookieless conversion check box.

In general, no. Enabling cookieless conversion doesn't replace cookie-based conversion, but rather increases the total number of conversions you can track, so there's no harm in enabling it.

If for some reason you want to only track cookie- or or device-ID-based conversions, turn off cookieless conversions at the creative level, and when you're setting up your tactic, select Target only devices with a user ID on the Devices tab.

In very rare cases, our link decoration might conflict with how the advertiser site is coded. This will be clear and obvious when you preview and test the creative after uploading it, as the ad will not click through correctly. If this occurs, turn off cookieless conversions for the creative by clearing the Enable cookieless conversion checkbox in the ad's settings.

At the end of the day, conversions are conversions regardless of whether they are tracked using a cookie ID, a mobile advertising ID, postback, or cookieless conversion attribution. Our optimization algorithms treat cookieless conversions the same as any others, so there is no impact on optimization and CPA goals.

Yes, conversions attributed using cookieless conversion will be reported in all Basis reporting as usual, including reports, analytics, insights, and Data Canvas.

If you want to see which conversions were attributed using cookieless conversions specifically, use the Conversion Details DSP report. This report includes a column that indicates how conversion attribution occurred.

If you're using display ad tags Campaign Manager 360, no additional steps are required. If you're using video or audio VAST from Campaign Manager 360, a small additional step is required in Campaign Manager 360 (FIXME: link to details).

For other ad servers, additional setup steps might be required. Contact support for assistance.

No. If both Basis' cookieless conversion and Campaign Manager 360 Enhanced Attribution are enabled, there will be two link decorations, but each platform will operate independently to the same result. There is no conflict.

No, any user with DSP access can upload CRM fils and use CRM audience segments in tactics.

Yes, if you are a LiveRamp customer, you can continue to upload CRM data directly to LiveRamp and then push it to Basis DSP.

CRM list uploads support plaintext PII data or encrypted (hashed) data.

For plaintext records, we only support US-based ZIP codes, phone numbers, and street addresses. Additionally, we don't support any special characters such as quotation marks, ampersands, apostrophes, or letters with accents.

For encrypted records, use MD5, SHA-1, or SHA-256 to hash the data.

See CRM List Formatting Details for more information.

You can upload CSV files (maximum 150 MB) and XLSX files (maximum 40 MB). Each file must contain a minimum of 101 rows.

See CRM List Formatting Details for more information.

Currently, there is a limit of 3 million records per 24 hours per advertiser. Note that for XLSX file uploads, there's a limit of 1 million rows per file.

Match rates depend on the quality of the data in the upload file. In general, the highest match rate will be a combination of email addresses, phone numbers, full names, and ZIP codes.

In general, email addresses provide the highest match rates, followed by phone numbers, followed by a combination of name and ZIP code. We recommend including multiple high-quality data points to have the highest match rates possible.

Currently, there is a limit of 3 million records per 24 hours per advertiser. Note that for XLSX file uploads, there's a limit of 1 million rows per file.

Basis removes any duplicate records that are uploaded within a 150-day period. We remove any new records that have exactly the same data as ones that have already been uploaded, and we don't submit files that are duplicates of previously uploaded files.

Data processing times depend on the size of the uploaded file. The expected processing time for most files is around 20 minutes, after which the targetable audience will be available. For massive files that contain closer to 1 million rows, the processing time is closer to an hour.

You may notice that the number of matches for a given audience will change as the data is being processed.

We do not directly store any of your CRM data—the raw data that you upload is sent directly to LiveRamp and is never exposed to Basis Technologies. We only store the anonymized RampIDs that LiveRamp creates based on your CRM lists.

LiveRamp continually updates its identity graph with new data points, which can cause RampIDs to shift over time. While these changes are minimal and unlikely to impact campaigns in the short term, they might have an impact in the long term. After 150 days, you can re-upload your audience to refresh the data and ensure match rates remain high.

The date filter for CRM audiences displays the last 180 days by default to show the most up-to-date audience data.

Yes, CRM audience data is available in new DSP reports that pull audience data, such as Data Segment reports or Delivery/Performance reports.

There are some data differences between Data Canvas and Basis' other reporting tools, because Data Canvas only displays gross uncapped delivery measures, which means that over delivery is not an omitted Rate Type. Over delivery is a potential aspect of campaign performance, so it is reflected within Data Canvas.

Although you can't edit a template to create and save your own, after you have customized a template, you can use a dashboard that you've already created for a different client by duplicating the dashboard and selecting a different client from the Duplicate Dashboard modal.

However, you may see some errors within the visualizations, due to variations between campaigns and different data sets. Some customization to the tiles may be required. See Duplicating Data Canvas Dashboards for more information.

Due to variations between campaigns and different data sets, some customization may be required to set up the visualizations.

If it is taking a long time for a tile query to finish, whether when first loading or when editing the tile data, try shortening the date period within the tile by changing the Delivered Date filter located at the top of edit tile modal.

If you are having trouble sorting by month, it may be because you have data from multiple years. Check to see if you have included the Delivered Year field in the Data table, then sort by Delivered Year, then Delivered Month. See Sorting Data for more information about sorting fields in a visualization.

GBO creates projections for a tactic's potential spend. As with any projection, there is a level of uncertainty, and as a result GBO provides a buffer among campaigns in the group to that it reaches its spend. Group pacing and daily group budgets will always be respected. In other words, the total sum of the effective budgets for tactics will be greater than the daily group budget or group pacing, but actual spend should exceed them.

Algorithmic optimization and group budget optimization should not interfere with each other, but there may be conflict between GBO and machine learning optimization. For example, MLO may lower the volume for one of the tactics in a group, so GBO would be stuck in learning mode for that tactic. In this case, we recommend adjusting the tactic's settings to create more reach, increasing the minimum daily tactic budgets, or turning off GBO. If you use GBO and MLO, both features should target the same KPI.

When you enable GBO for a group, all of the tactics require a learning period before an effective budget is available. You should manually set a budget for the tactics to use during this learning period.

When using GBO, we strongly recommend that the KPI you select for the group aligns with the KPI for each tactic. For example, if you enable GBO and select CTR, build all of the group's tactics with CTR as their goal.

GBO applies a buffer to ensure that if tactics do not meet the daily effective budget, other tactics in the group will make up for it. If spend is not met even with this buffer, GBO will take this into account and reallocate the budget accordingly.

Note that GBO will not solve delivery issues across the entire group if the majority or all tactics are experiencing issues.

Whenever you change flight dates, GBO automatically adjusts the effective budget by the remaining days left in flight. This also occurs when you change the group budget.

To optimize a tactic, GBO requires a minimum amount of data for each tactic. Currently, the optimzer requires 5 events, $20 in spend, or 10,000 impressions to begin calculating new tactic budgets.

Check the campaign's previous plans - it's likely that this line item has an earlier contracted start date in those plans, and since that date has passed, you can't delete the line item.

After a campaign is approved, you cannot remove all of the line items from a property. If the line item you want to delete is the last one remaining in a property, you can't delete it. Instead, you can label the line item as Cancelled and zero the values out.

In a DSP plan, since it is a real-time bidding environment, you can only select the present or a future date as the start date.

Compared to direct plans, there isn't as much flexibility when it comes to editing DSP line items, because DSP is a real-time bidding environment. DSP line item fields lock after the earliest contracted start date. The only field you can edit is the Gross.

If the earliest start date has already passed, then the rate locks in and you cannot edit it. One solution would be to cancel the line item and create a new one. However, there are some things to consider.

If the line item is direct, search, or social:

• Have any placements been exported from the line item you are about to cancel? If so, you won’t be able to map these placements in the new line item you are about to create. You can use an uploaded file though to bring in delivery data from these placements over to the new line item.
• Has the end date for the original line item passed, and was it in a previous month? If so, you won’t be able to select that end date. You can only select an end date in the current month. If the end date is still in the future, then you can select it when you recreate the line item.

If you want to proceed with canceling the line item, first cross off delivery metrics in Analytics. If you're able to unmap delivery sources, then just unmap them instead. When delivery in Analytics shows 0, create a revision and cancel the line item in that revision.

If the line item you want to cancel is DSP:

• Is there already delivery associated with your tactics? If so, you cannot cancel the line item unless you set the tactic to offline and cross off delivery in Analytics. If you do this, you cannot bring the tactics back.
• Is the start date in the past? When you create a new DSP line item, the start date must be today's date or a date in the future.

For DSP plans, if a wrong rate was assigned, it’s best to just turn the tactics off, end the line item, and then create a new one from scratch with the proper settings.

The ad server and Basis DSP are two different platforms with different counting methodologies. An ad server’s filtering methodologies (how it determines an invalid impression or click) and measurement methodologies (how it counts an impression or click) differ from the DSP's, so it's normal to see differences. When it comes to Campaign Manager 360, discrepancies of up to 20 percent are normal.

If you have a DSP line item that has Campaign Manager 360 delivery sources mapped to it, and you are seeing a huge discrepancy, here are a few things to consider:

• Make sure you have the right placement IDs mapped to that line item. If these were brought in via one way delivery, ensure you have the right placements mapped to the line item. If the wrong placement ID is mapped, or one or two placement IDs are unmapped, this can cause you to see very large discrepancies.
• If you exported the placement IDs out of Basis, check that delivery data is pulling correctly. You can pull a daily delivery report from Campaign Manager 360 and compare a Campaign Manager 360 placement ID with what is pulling in Basis for that ID. If it doesn't match and there is a delivery lag, contact Basis Support to assist you in getting the data updated. Provide a daily delivery report from Campaign Manager 360 with placement IDs along with an example of a placement ID where all delivery data is not pulling in Basis, if possible.

If there is no delivery data lag, and the correct placement IDs are mapped to the line item, then there just really is a discrepancy with your ad server numbers.

If the DSP is counting more impressions than the ad server (Campaign Manager 360), then you most likely uploaded one or more ad tags without the timestamp macro {ts}. The timestamp macro allows Campaign Manager 360 to track every impression per user. Without this macro, Campaign Manager 360 caches the user and only counts the first impression served per user, while the DSP will count all of them.

To address this issue, turn everything off in the DSP and ad server, generate new tags with macros in place, and use those new tags to run in the DSP and ad server.

Other things to consider when the DSP generates more impressions are:

• There's some sort of targeting being layered on in the Ad Server itself. For example, any targeting like frequency capping, geo, or domain blocking will contribute to a discrepancy.
• There is a creative running like an MP4 or HTML5 that is being hosted on the DSP and does not report back to the ad server.
• If they are using IAS Campaign Manager 360 tags, a timestamp macro is not required. If it includes an IAS snippet, this could be an issue for discrepancy. When IAS determines that the content of the page is not desirable (using their own methods), they show "cloud ads" instead of the actual ad. IAS doesn't count cloud ads, but the DSP does count them as we tried to serve the ad and our impression tracker was fired.
• Using systems like IAS or DoubleVerify's real-time ad placement verifications tools can cause a discrepancy. The DSP will count an impression, but these systems may not count that impression if it doesn’t meet the client’s requirements.
• We normally suggest when clients use DoubleVerify creative verification that they also layer DoubleVerify Brand protection segments that match to help reduce the discrepancy the systems see. However, since brand protection is based on historic data, and ad verification in the tag happens in real time, there is no way to guarantee they'll always match. That said, a discrepancy is always expected when using tools like this.

If the ad server is generating more impressions than the DSP, it could be that the tags are running in places other than the DSP. This is something you have to check with the ad server.

If you are seeing a discrepancy in clicks, check that the click macro was implemented properly to make sure your creatives are tracking clicks. Ad servers generally pull in more clicks than the DSP, usually due to testing on their end combined with the fact that the DSP filters out clicks that are determined to be invalid.

Finally, when comparing data between Campaign Manager 360 and the DSP, consider the timezone and date range when you pull the report. If these are not the same, then you will see a discrepancy.

Market Trends data is an aggregated anonymized historical data set collected across all of Basis.

We aggregate and average the data in Market Trends from at least 3 unique brands and at least 5 line items to ensure that there is no association between the data and an individual organization.

If we cannot anonymize the data because the available data does not meet the minimum requirements, we do not display a graph. This can occur if you select a short time frame or a niche vertical. If this happens, we recommend trying different filters.

Yes, the data in Market Trends is aggregated and anonymized to prevent the identification of any Basis customer or client of a Basis customer.

The use of aggregated and anonymized data to help improve products, understand customer use, and observe trends is customary and industry-standard for B2B SaaS platforms. Additionally, Basis agreements expressly permit this type of data use.

The usage of the data is fair use and is anonymized to ensure that no single organization's data is exposed. Please reach out to your CSM with any concerns.

The data updates approximately once per month. The Data Through date in the upper-left corner indicates the last time the data was updated.

The graphs show median values to reduce the effect of outliers.

Market Trends does not currently support exporting any graphs or data. If you want to repurpose any information from market trends, take a screenshot of the relevant data.

No - to provide fair comparisons for benchmarks, calculations involving spend use Net Media figures, which do not include margins or ad serving.

Basis introduced the new location targeting on January 27, 2021. The new targeting taxonomy affected countries, regions, and cities, but not DMA codes, ZIP/postal codes, or hyperlocal targets.

If you're using a tactic or tactic template set up prior to January 27, 2021, your locations may be marked as Hidden or Unavailable, as some of these locations may not exist anymore and aren't available for bidding.

Hidden locations are location targets that are still viable. You can't select hidden locations when setting up location targeting rules, but bidding continues on saved tactics that already target the hidden locations.

Unavailable locations have been removed and can't be targeted. No bidding occurs on these locations.

See Hidden and Unavailable Locations for more details.

If you want to edit a tactic that was set up using the old location taxonomy, you will have to re-select all locations using the new taxonomy. If you want to add new locations, you must remove all of the old locations first, and only use the new location taxonomy.

When you bulk edit locations, you can only include tactics with legacy location targeting if you choose to bulk replace the tactics' locations. You cannot bulk add locations to tactics that have legacy locations.

Location sets that contain legacy locations cannot be added to new tactics. You must recreate old sets using the new taxonomy.

You can copy and paste a tactic that includes legacy location targeting, but as with all other tactics, you must remove the legacy locations if you want to edit the tactic's location targeting.

If you choose to edit the tactic before pasting, the location targets won't carry over, and you will have to add targets using the new taxonomy if needed.

If you create a new tactic from a tactic template that uses legacy location targeting, the new tactic will not include any location targets. You must add locations using the new taxonomy.

Yes, you can add geopolitical locations to new or existing location sets and tactic templates.

Currently, US political districts are supported in geo reports as a tactic dimension, with and without conversion pixels. See Geo Reports

Yes, as of May 2022, we offer targeting for state legislative districts. This includes state senate and state house targets.

The only geopolitical location targets we support at this time are in the United States - US congressional districts and state legislative districts.

When you get that error message, it means that the delivery for your revised line item is less than what was actually delivered so far. To fix this, you must use the amount that was delivered or more. You can see the actual delivery in Analytics.

If it is crucial that you use a lower delivery in the revision, even though it is less than what was delivered, you can cross off delivery metrics in Analytics to work around this restriction. After you do this, you can go back and approve the revision. After approval, go back to Analytics and check impressions for that line item's sources to bring in delivery data.

Basis requires that you have a Manager account - verify that your Google Ads account is a Manager account.

Try connecting and reconnecting the Google Ads account. If this doesn't help, it could be that your account does not have API access. Reach out to Basis Support to request API access for your account.

Remove Basis from your Facebook account and then try again.

1. Go to https://www.facebook.com/settings?tab=business_tools and remove Basis.

2. Open Basis and reconnect your Facebook account.

   1. Go to My Settings.
   2. Open the Third Party Accounts tab and click Add account for Facebook. Log in to your Facebook account in the new window that opens.
   3. Click Edit access and make sure your account is enabled.

3. Click Continue and then allow Basis to manage your Facebook ads to finish connecting your account.

If your creative was rejected for the reason "Duplicate Frames / Please resubmit in native frame rate to remove stutter during playback", it is likely that the video was compiled from different videos that were recorded in different frame rates and then converted to one frame rate. This results in duplicate frames and stuttering.

For example, to convert a video from a lower frame rate (such as 24 fps) to a higher one (such as 29.4 fps), the converter needs to add 6 more frames per second to compensate for the difference. It usually achieves this by taking a group of 4 frames and duplicating the last one to create a block of 5, for a total of 30 frames per second. The duplicated frames cause the final video output to stutter, which premium CTV inventory doesn't approve.

To fix this, the video needs to be in its native frame rate rather than compiled from different frame rates. Upload the fixed creative file as a new ad and link it to your tactic so that the CTV publisher can review and approve it.

It is common for video tactics to overspend.

This issue is complicated as there's a delay between a video being shown and us counting it in Basis because of how video players report data. Due to the delayed win notification we get from the publishers/exchanges (in some cases, it may take up to 4 hours), there's a greater chance that a video tactic will overspend if it's running with no pacing as the system will have gone past the budget by the time it tries to stop spend.

When running video tactics, you should check each tactic once they launch and apply pacing to any tactics that see a lot of volume and hit their spend cap early in the day.

Unless there is delivery being reported for the desired conversion through a delivery source linked to a campaign in the account, it will not be listed for conversion tracking. Make sure the delivery sources you have for your campaign are pulling the conversions you want to track.

Agency billing info is required when proceeding without an IO because we need to know where to send the bill. However, it is up to you and your organization whether you assume responsibilty for the bill or if you want to bill the client a different way outside of Basis.

To fill out the Agency Billing information, go to My Organization > Profile and fill out the information under Billing Information.

One thing you can do is increase your default bid. This allows the tactic to bid more aggressively, helping open up more inventory, increasing your chances of winning more impressions.

Another option to look at is pacing. If you have a daily budget, you may want to turn pacing off, as this will also help the tactic bid aggressively.

You can also consider your targeting options. For example, we do not recommend combining audience and contextual targeting, as this may limit your tactic's ability to win impressions.

If you are targeting multiple audience segments and connecting them with an AND rule, this will impact your scale. The same applies if you are targeting multiple contextual segments and connecting them with an AND rule.

If you are targeting audience segments, you may want to look at the reach. A low reach will also impact scale. If you are targeting first party audience data, we recommend that you have at least 1000+ visitors added to scale. Consider enabling cross device to help increase reach when targeting first-party data.

Exchanges or SSPs require DSPs to accurately report the brand domain and verticals in bids. Most exchanges trust that DSPs are doing this accurately, and use this information to enforce publishers’ blocking requirements. As such, we need to know the brand domain and verticals for each ad.

We use a combination of human auditors and automation to enforce ad quality rules. Automation drastically speeds up the auditing process, which ensures that we can allow ads to go live as quickly as possible. However, detection of the brand and vertical for an ad is challenging, and the best technology for detection is still imperfect. To overcome this, we require this information from the user.

The brand domain should be a domain that represents the brand being advertised, without www. It's not exactly the landing page domain, though in many cases, the landing page domain is appropriate. It should also not be a full URL. For example, an ad for Ford should have an advertiser domain of ford.com. This is true even if the ad clicks through to Ford’s Facebook page. facebook.com wouldn't correctly reflect the brand of the ad, but ford.com does. For mobile app install ads, the domain should be that of the app developer. For example, zynga.com for Words with Friends.

If we don't have an accurate brand domain and categories for the ad, publishers’ blocking requirements won't be respected. For example, if a publisher blocks automotive ads, and the ad isn't correctly declared as Automotive, then the ad might be served anyway. Because of the automated nature of real-time bidding, very large numbers of impressions that violate their rules can easily be served very quickly. Publishers take this seriously, and it'll result in a complaint to us. Depending on the nature of the violation, it can be considered a very serious incident. For example, if an alcohol ad is served and the publisher doesn't allow it, it could be deemed so serious that the publisher bans us from bidding. This would prevent all of our customers from buying from that publisher.

Our ad quality auditors spot check values entered. If there are serious deficiencies or signs of intentional misrepresentation, automated ad approval privileges will be revoked.

Despite the above, the important thing is to make an honest effort at correctly representing what the ad is. Choose the most specific category that represents the ad. Use a parent-level category if there isn't a more specific category that seems to apply, such as Home & Garden > Appliances versus Home & Garden. Select multiple categories, if applicable. If users still aren't sure, they can ask the support team for advice.

The following Sensitive Categories are of critical importance to select (if such content is present):

• Alcohol

• Cannabis

• Cryptocurrency

• Firearms

• Gambling

• Politics

• Prescription Drugs

• Sexuality

• Tobacco

Publishers are particularly concerned about ensuring such ads are correctly categorized as there may be legal or regulatory requirements they must respect, or users may be very sensitive to ads from these categories.

There are two brand verticals for political advertisements.

• If the ad is a paid political advertisement that falls under the DAA Self-Regulatory Principles for Political Advertising or state legislation related to political advertising, use Sensitive Categories > Political (Elections).

• If the ad is for a politically related issue but doesn't fit into the above, such as get-out-the-vote campaigns and legislation advocacy, selectSensitive Categories > Political Issues (Non-Election).

See Political Campaigns and Uploading Political Ads for more information about political advertising.

Not necessarily. Not all ads can be audited automatically, and manual human checks still occur to ensure accuracy. Customers observed to self-report these values accurately will have most of their ads go through automated auditing. However, all customers benefit from faster turnaround due to fewer ads requiring manual auditing. even if a given ad doesn't receive an automatic audit.