The following instructions are for Global Support to provide to the client. The client should complete the integrations themselves. Please reference the troubleshooting guide at the bottom of the page if you have any trouble delivering these instructions.
| Note |
|---|
IMPORTANT – PLEASE READ The AdSet names in the networks MUST be named according to the following naming convention: Free (X Codes) {Source Code}:{List}:anything else
{Source Code} {List} anything else
{Source Code}|{List}|anything else Example:
Paid (Non-X Codes) {Promo Code}:{Primary Item}:anything else
{Promo Code} {Primary Item} anything else
{Promo Code}|{Primary Item}|anything else Example:
|
...
Getting Started With Stitch
...
| Note |
|---|
IMPORTANT – PLEASE READ The AdSet names (Adgroup on Google Adwords) in the networks MUST be named according to the following naming convention: Free (X Codes) {Source Code}:{List}:anything else
{Source Code} {List} anything else
{Source Code}|{List}|anything else Example:
Paid (Non-X Codes) {Promo Code}:{Primary Item}:anything else
{Promo Code} {Primary Item} anything else
{Promo Code}|{Primary Item}|anything else Example:
|
...
| Note |
|---|
IMPORTANT – PLEASE READ BI will drop and reload all costs entered in client Google Sheets 3 months back (current month + the previous 3 – ex. during October we will drop and reload all costs for July, August, September, and October) everyday. Any changes during that 3 month window can be made within the google sheet – no BI notification or intervention required. If a client has a change that needs to be made for the current calendar year outside of that 3 month window, then they can do so in the sheet. HOWEVER, they have to submit a ticket and coordinate with BI so that we can temporarily expand the cost pulling window to pick up the corrected costs. It is recommended that clients do not remove any costs from the google sheets without oversight. If needed, the client can work with their CSP to organize a cost purge to delete and catalog historical costs. Timing:
|
Global Support - Stitch Integrations Troubleshooting Guide
First, check to see if the account is setup in Stitch by looking to see if the integration is setup.
If it is setup, does it follow the correct naming convention?
Facebook - {Affiliate Name/Abbreviation}_facebook_{identifier}
Google - {Affiliate Name/Abbreviation}_google_{identifier}
If yes, are the correct tables checked for Tables to Replicate?
Facebook: ads_insights
Google: AD_PERFORMANCE_REPORT
Bing: ad_group_performance_report
If the correct tables are checked, are the correct fields checked for tracking?
Facebook:
adGroup
clicks
cost
Day
impressions
Google:
Ad Network
Campaign
Clicks
Cost
End Date
Start Date
Impressions
Bing:
Report_datetime (default),
AccountID (default),
AdGroupName,
Clicks,
Impressions,
Spend,
TimePeriod (default)
If all of the above is setup correctly please reach out to the client and ask them to provide an export out of their ad platform of the promo/source codes in question to see if the ad set names are correct and follow the following naming structure:
Free Source Codes
{Source Code}:{List}:anything else
{Source Code} {List} anything else
{Source Code}|{List}|anything else
Example: X300W100 LIBWEALT This is free form text
Paid Promo Codes
{Promo Code}:{Primary Item}:anything else
{Promo Code} {Primary Item} anything else
{Promo Code}|{Primary Item}|anything else
Example: POXFV100 OXF This is free form text
If the ad set names are not in the above format you will need to have them correct the ad set names and then the ad spend should pull in on the next run.
If the next run does not balance out the costs you will need to ask the client to do a daily export out of their ad platform (Facebook/Google/Bing) which includes the start/end date, the ad name, and the ad spend. They will then need to submit a support ticket which should be escalated to the D&A Team so that they can update the costs tables with the spend provided from their ad platform. PLEASE NOTE: This situation should be rare, but from experience this is what can cause ad costs to not match what was in stitch. They had more than one item or list associated with one code, causing duplicate costs.
| Note |
|---|
Make sure the replication frequency is accurately setup. If it is set to the default it will create multiple rows which will end up impacting how the company is billed by Stitch. It will not return an error, but it is worth noting during the setup/troubleshooting process
|