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.
Getting Started With Stitch
To begin, Click Here to sign in to Stitch with your OneLogin credentials. You’ll want to make sure you also have all necessary logins for the social platforms you will be integrating (i.e. Facebook, Google, etc.)
Once you’ve set up your account and signed into Stitch, you’ll begin by selecting an integration.
Facebook or Google Adwords are often a good place to start; however, Stitch allows for integrations with Bing, Outbrain, and more.
These integrations will then be configured one at a time. Each has its own specific details that we will cover below.
Setting Up a Facebook Integration
To set up a Facebook Integration, simply select the Facebook logo from the menu shown above. This will open the menu shown here (click to expand) where you will enter the following details:
Integration Name:
{Affiliate Name/Abbreviation}_facebook_{identifier}
Attribution Window:
28 days
Sync Historical Data:
Set to one month before start date
Replication Frequency:
24 hours – Anchor Time: UTC 0:00
Once entered, you will be asked to login to your Facebook to confirm your account. From there, you will choose the Tables and Attributes to replicate. Below is a reference for which tables and fields should be selected.
Table to Replicate:
ads_insights
Fields to Track:
ad_id
adset_id
adset_name
campaign_id
Clicks
date_start
date_stop
impressions
spend
Once selected, your Stitch x Facebook integration should be complete. If you have any issues with this process, or have more questions, please contact Global Support.
Setting Up a Google Ads Integration
Much like a Facebook integration (or any integration with Stitch) we’ll begin with the integration details. For Google Ads we will use the following:
Integration Name:
{Affiliate Name/Abbreviation}_google_{identifier}
Sync Historical Data:
Set to one month before start date
Replication Frequency:
24 hours – Anchor Time: UTC 0:00
Once again, after initial configuration you will be asked to sign in to your Google Ads account. Once signed in, you’ll navigate to “Tables to Replicate.” Below is a reference for which tables and fields should be selected.
Table to Replicate:
AD_PERFORMANCE_REPORT
Fields to Track:
adGroup
clicks
cost
Day
impressions
Once selected, your Stitch x Google Ads integration should be complete. If you have any issues with this process, or have more questions, please contact Global Support.
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
OR -
{Source Code} {List} anything else
OR -
{Source Code}|{List}|anything else
Example:
X1234567 Listname supportingtext
Paid (Non-X Codes)
{Promo Code}:{Primary Item}:anything else
OR -
{Promo Code} {Primary Item} anything else
OR -
{Promo Code}|{Primary Item}|anything else
Example:
E1234567 Itemname supportingtext
Setting Up a Google Sheets Integration
Unlike Facebook and Google Ads, clients will not be allowed to manually create Google Sheets - the client will set up the integration but Global Support will create/provide the google sheet when requested. The main reason for this is that the set up of the Google Sheet column titles is very specific and if not matched exactly, the integration will fail.
In order to integrate with Google Sheets, a sheet will need to be created with the sole purpose of uploading costs and all of the headings shown above must be included exactly as is (case sensitive.) This sheet will also need to be shared with the BI team. We do not recommend adding extra column headers to these sheets; however, if you have a new use case that requires this, please reach out to your CSP.
Once the Google Sheet has been created and the headings are validated, you will configure your integration with the following details:
Integration Name:
{Affiliate Name/Abbreviation}_google_{identifier}
Spreadsheet ID:
Go to Google Sheets and log into the Google account associated with the spreadsheet you are looking to integrate.
Open the spreadsheet that you want to use in the integration.
Your Spreadsheet ID is within the URL to the webpage. In the image below, the portion of the URL within the blue box is the Spreadsheet ID. Keep this readily available to continue with the integration.
Sync Historical Data
Set to one month before start date
Replication Frequency
24 hours – Anchor Time: UTC 0:00
Once all of the integration details have been entered, you will be asked to sign into your Google account to verify the integration. If you have any issues with this process, or have more questions, please contact Global Support.
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:
Costs are pulled at approximately 8am EST.
Costs entered in by 8pm EST will show up in BI reports (ThoughtSpot and Qlik dashboards) 2 days later. Anything entered in after 8pm EST will show up 3 days later.
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.
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.