In general, "first_open" is the default event. Singular uses it to report only the first sessions of each device to GMP. GMP then determines whether they will claim those first sessions as their own for install attribution purposes.
The "session_start" event is manually configured, which can be mapped to any event in Singular, such as "__SESSION__".

In this example, this event tracks every session reported and sends it to Google Marketing Platform under “session_start”.

For both CM360 and DV360, we do not receive Campaign Name data from the attribution integration. This means that in order to populate the Campaign Name correctly, we use network data. However, when campaigns begin this may take a day or two to occur.

You may see data discrepancies for the following reasons:

• GMP self-attributes substantially more impression-based touchpoints than clicks. So other partners may be awarded the install if they generated any click at any time within the relevant attribution windows. See how Singular prioritizes touchpoints.
• GMP-claimed impressions can be outside Singular’s default 24-hour view-through window, causing their reported install numbers to be higher. As a result, their events count will also be higher. Understand attribution lookback windows.
• We use last-touch attribution with GMP.  If there are other partners with closer touch points, they will win the attribution even if GMP claims it as their own similar to other SANs.
• GMP may have claimed certain users in the past, while Singular attributed them to other partners or Organic. In such cases, GMP will continue to count their events as their own. In Singular, those users will continue to be tracked under their originally awarded partners, unless a re-engagement attribution has occurred.

• GMP does not currently support MMP measurement for iOS or Android conversions from CTV campaigns

 

When and how to collect user consent signals for EEA users should adhere to your business' and apps requirements for user privacy. Consult your business' legal counsel to understand how your app needs to adhere to internal privacy policies and privacy regulations such as GDPR, ePrivacy Directive, and the Digital Markets Act.

If you decide to collect user consent signals, it is generally recommended that:

• User consent signals be set only when the user has explicitly opted-in or out. It is recommended to leave LDS unset if a user did not make a choice. The absence of a user signal may be important.
• User consent signals are commonly collected in "Privacy Choices" or "Privacy Settings" during the app experience.
• When possible, and depending on your app's consent prompt design and strategy, surface privacy prompts early in the app flows to ensure Singular and other SDKs can collect the user consent signal as early as possible
  
  

If your business determines that EU privacy regulations for EEA users apply to your app: Implement the Singular SDK/S2S "Limit Data Sharing" feature based on the consent prompts your app presents to these users.

• Using Singular's iOS SDK:
  

  limitDataSharing Method
  Description	Notify Singular of user consent (opt-in) for sharing private data. Use limitDataSharing:NO to indicate that the user consented (opted in) to share their information. Use limitDataSharing:YES if the user did not consent.
  Signature	(void)limitDataSharing:(BOOL)shouldLimitDataSharing;
  Usage Example	SwiftObjective-C // User has opted into sharing data Singular.limitDataSharing(false) // User has opted into sharing data [Singular limitDataSharing:NO];

• Using Singular Android SDK:
  

  Singular.limitDataSharing Method
  Signature	Singular.limitDataSharing(boolean shouldLimitDataSharing) Use Singular.limitDataSharing(false) to indicate that the user consented (opted in) to share their information. Use Singular.limitDataSharing(true) if the user did not consent
  Description	Notify Singular of user consent (opt-in) for sharing private data.
  Usage Example	// User has opted into sharing data Singular.limitDataSharing(false);

 

If your business determines that EU privacy regulations don't apply to your app, you can opt-out of EEA user consent signals in Singular. check the "EEA opt-out" option under the "User Privacy" section in the partner configuration. LDS and user consent signals are not used by Google with this option.

• Implementing LDS for EEA users is not required if using this option
• This option can be enabled prior to Google's March updates going live

Singular's Limit Data Sharing (LDS) is a feature that allows app developers to pass each user's user consent signals to Singular. LDS is set per user and can be set before or after SDK initialization. LDS is used in Singular User Privacy Postbacks and passed to certain partners like Google, who use it to comply with their own data practices.

See "Supporting User Privacy Choices with Limit Data Sharing FAQ"

Google lists Consent Management Platforms (CMPs) that support the required user consent signals. If you use one of these CMPs, you can extract the user consent signals and pass them through Singular's LimitDataSharing feature. 

 (Coming soon) The Singular SDK/S2S will support an optional mode to automatically ingest user consent signals from these certified CMPs (via the TCF 2.2 standard).

Starting March 2024

For EEA users that opt-out to user consent:

• User-level attribution to Google Marketing Platform campaigns will not be available in Singular.  Google won't be able to report these attributions to MMPs
• Google Marketing Platform won't be able to use this users data for advertising purposes

For EEA users that opt-in to user consent:

• User-level attribution to Google Marketing Platform campaigns are possible
• Google Marketing Platform will use this data for advertising purposes