Which Quantcast Campaign objective(s) work with Verified by Q?
Conversions
Traffic (see limitations section)
Where do I find GA4 Measurement ID and API Secret?
See Measurement Protocol documentation here.
api_secret: The API Secret generated in the Google Analytics UI.
To create a new secret, navigate to Admin > Data collection and modification > Data streams > choose your stream > Measurement Protocol API secrets > Create.measurement_id: The Measurement ID associated with a stream, found in the Google Analytics UI under Admin > Data Streams > choose your stream > Measurement ID.
The measurement_id isn't your Stream ID.
Where do I find Attribution settings in GA4?
Admin > Data Display > Events > Attribution settings
Will GA4 automatically start assigning credit to (beta)Verified by Q?
No. Ensure the option Paid and organic channels is selected for Channels that can receive credit in the Attribution Settings page for Verified by Q to receive credits.
Does changing the Reporting attribution model in Attribution settings affect the Traffic Acquisition report?
The Traffic Acquisition report relies on session-scoped traffic dimension - session source, and is unaffected by changes to the reporting attribution model.
Changes to this setting affect the key event attribution that powers the Key Event Attribution Path report.
How do I know Verified by Q integration is set up correctly?
Once your Quantcast campaign starts driving conversions, the integration will submit MP events for visits associated with the conversions. You should expect to see verified_by_q_visit events in the Engagement > Events section of GA, which may take up to twenty-four hours.
Can I expect session numbers in GA4 to match with Quantcast Campaign’s conversion number?
No.
A conversion in a Quantcast conversion campaign is an occurrence of a specific event (purchase, add_to_cart, etc.) on the website, attributed to one of the campaign’s Ad Sets.
In GA4, a new session is initiated when a user views a page, and no session is currently active. There is no limit to how long a session can last. This session may encompass multiple events on the website (landing page, plus other parts of the website, plus purchase/add_to_cart). The non-direct last-click attribution model for a session is valid for the key event lookback window, with a default of 90 days. Two consequences of this:
Potentially multiple conversions recorded in Quantcast can be part of the same session. Meaning, you may see fewer sessions in GA4 than conversions in Quantcast.
Verified by Q will continue to receive session credits in GA4 until a new non-direct last-click source is recorded or the lookback window expires. Meaning, you may see more sessions in GA4 than conversions in Quantcast.
What is the source/medium set by Verified by Q?
For a conversion campaign in Quantcast, you should see a source/medium that says quantcast / conversions_campaign in GA4.
For a traffic campaign in Quantcast, you should see a source/medium that says quantcast / traffic_campaign in GA4.
Can I customize the source/medium coming from Verified by Q?
No. This is automatically determined by our system based on the campaign.
Why am I not seeing Revenue numbers in GA4 against Verified by Q source/medium?
Quantcast does not control revenue data in GA4. Please work with your client to ensure their GA4 is set up correctly to track revenue.
Is it possible that Quantcast is capturing credit from other channels in my GA4?
No. Verified by Q integration will allow GA4 to assign credit to Quantcast only where the channel would have been Direct/None, i.e, traffic that is unclaimed by any other channel. Traffic that is already assigned to a valid channel is unaffected by this integration.
When using sGTM with FPID, do I need to worry about duplicate events from Live Tag and sGTM integration?
No. These two events are independent and do not lead to duplication. Live Tag events are standard pixel fires measuring activity on the web page. Live Tag’s sGTM integration is primarily designed to collect FPID, enabling your GA4 integration to work in the context of sGTM with FPID.
Will I see new events from the MP events Quantcast submitted?
Yes. MP events show up as new events in GA4 under the “Engagement > Events” section. You should be able to identify them by the name verified_by_q_visit.
Will I see additional sessions from the MP events Quantcast submitted, or will I just see appropriate credit assignments to sessions in GA?
Yes to both. MP events themselves do not have a utm_source/medium. So you will see new sessions from them recorded against “(not-set)” source. Ignore these counts from your overall session count. But the same MP event allows GA to apply its session-sourced attribution logic and assign credit to Quantcast when it sees appropriate.
Under Acquisition → Traffic Acquisition Report, update the grouping by Session Source/Medium. Then filter the rows to just “not set” source. Click the plus sign, then add Event as a dimension. You will see the event name verified_by_q_visit. This shows the additional sessions created from this integration. You may have many other events contributing to “(not set)”, but they are unrelated to Verified by Q.
