Important Note: Reminder that Google Analytics 4 replaced Google Analytics Universal on July 1, 2023. To ensure your performance tracking data can continue to be sent to Outbrain DSP, please make sure to switch your connection from Google Analytics Universal to Google Analytics 4 API in the Campaign Settings. To learn more about how to make the switch, please follow the steps described HERE.
Outbrain DSP leverages the Google Analytics API to ingest your post-click metrics. This guide walks you through a simple two-part setup process in Outbrain DSP and your Google Analytics account. Make sure to follow both of them accordingly.
Make sure tracking parameters are appended to every ad URL when using click trackers/commands: To track first-party analytics data (Google Analytics), Outbrain DSP has to append its tracking parameters to every content ad URL. The parameters are expanded on the DSP's redirector and captured by the analytics on the landing page. Learn more here.
Part 1: Setup in Outbrain DSP
1. Select the Campaign that you want to integrate with Google Analytics.
2. Open the Settings drawer.
3. Mark the checkbox to Enable Google Analytics Performance Tracking in the Performance Tracking section.
4. Input the following information:
Reporting Type: API
5. Click the Save button.
Part 2: Setup in Google Analytics
1. Navigate to the Admin section of the Google Analytics dashboard.
2. Click on the Property Access Management
3. Add a new user by clicking the + icon.
4. In the Add Roles and Data Restrictions window, enter DSP's tracking email account-13@zemanta-api.iam.gserviceaccount.com, and select the Viewer role for this case.
If you experience an issue with the above tracking email, please use account-14@zemanta-api.iam.gserviceaccount.com
5. Click the Add button, and you're all done!
Outbrain DSP can now automatically ingest your post-click metrics in real-time for all enabled campaigns. If you ever need to delete this user, simply log into your account permissions and select Delete user.
Adding Custom Views in Google Analytics Property
If you are creating custom views in the Google Analytics account for the property that Outbrain DSP is ingesting and want it to ingest all of the data comprehensively, you have to follow the rule below.
By default, Outbrain DSP can ingest only the first view inline. To pull the whole data set to effectively optimize your campaign goals, leave the first unfiltered view untouched.
Google Analytics creates the first unfiltered view by default for your property. Do not delete or add filters to this default view. We suggest you add new views instead of editing the default one.
PLEASE NOTE: If you have already modified the default unfiltered view and want to ensure Outbrain DSP ingests all of the important reporting data, contact your CS rep or use the chat in the DSP dashboard.
Important:
The web property ID must be on the actual landing page. On the landing page, right-click and select Inspect element. Go to the Network tab, reload the page, and search for UA-.
Ensure the event is enabled and that Outbrain DSP has access to the Web property ID in the Google Analytics account. The DSP needs access to Read & Analyze at the web property ID level. Grant access.
Check if your Google Analytics tracking parameters are appended to the URL. This is the same process as for the Automated email reports.
Data Use and Privacy
Google formally approves Outbrain DSP's access to Google Analytics data.
Our system will only read DSP-related data as it filters out data signals that do not contain its click ID (zpbid) or Outbrain DSP Performance tracking codes (_z1_msid, _z1_adgid, _z1_caid) in the landing page URL.
For optimization and audience segment-building purposes, Outbrain DSP will only use contextual data based on clicks (i.e., time of day, section, browser, etc.) and will not use the user's personal data.
You can create a custom filter inside Google Analytics that automatically collects traffic generated only by your Outbrain DSP campaigns. To create the filter, navigate to the Filter section in the view in which you want to create it and then include _z1_|zpbid| in the Filter Field.
PLEASE NOTE: When using workarounds, include the filter: _z1_|zpbid|.*z1[0-9]+[a-zA-Z].+?1z.* in the Filter Field.