See How to Track In-App Events.

For Singular Attribution customers, standard events are events with pre-defined names that are commonly supported by ad networks for reporting and optimization.

Standard events reported by your app through the Singular SDK are created automatically in the Events page, saving you time when you onboard.

For more information, see How to Track In-App Events and the list of standard events supported by Singular.

Singular recommends using standard events in your SDK/S2S integration (rather than events with custom names and attributes) whenever possible.

When you integrate a Singular SDK or S2S into your app, Singular tracks several types of in-app events automatically, without you having to add code to send them to Singular when they happen.

These built-in events will appear in:

• The Events page
• User-level attribution logs (see Export Logs and User-Level Data FAQ)
• Partner postbacks (if the partner is receiving the auto-generated event name)
• Internal BI postbacks

See the list of built-in events.

If you use Singular Attribution, some of the in-app events that your app sends to the Singular server will be tracked automatically with no need for further configuration on your part:

• Built-in events such as __REVENUE__ (see Built-In Events for the full list)
• Standard events (see What are standard events?)

If your app sends custom events (meaning events with custom names and attributes, as opposed to standard events), these are not added automatically to the Events page, and you need to add them manually to have Singular group them by cohort and aggregate the data for analysis and reporting.

If your app sends a large number of standard events, some of them may not be added automatically either, due to the limitations on the number of events in the Events page. Learn more about the limitations.

Note that all the in-app events that your app sends to the Singular server appear automatically in the user-level attribution logs (see Attribution-Logs">Exporting Attribution Logs).

The Events page is populated with events received from the Singular SDK. If you don't see your events, check if you have:

• Correctly integrated the Singular SDK in your app
• Defined your events in the SDK
• Correctly added your apps in Singular.

Cohort events are in-app user events such as sign-ups, purchases, leveling up in a gaming app, etc. You can have Singular track and aggregate any of these events by cohort, where the cohorts are based on the date of install (see What are cohort metrics in Singular?).

In other words, cohort events answer questions such as:

• In the group of users who installed the app on a certain day, how many users made a purchase within 7 days after installing?
• In the group of users who installed the app on a certain day, how many users leveled up within 14 days after installing?

See also: Ways of Measuring Events (Cohort vs. Actual, Unique, First).

Cohort events are defined based on information from your attribution tracker. Any user interaction that your app reports to your tracker (sends an event to the tracker) can be used to define a cohort event so you can track the stats for it in aggregate.

To start tracking events:

1. If you use Singular for attribution, you first have to make sure that your app reports in-app events to Singular through the Singular SDK or S2S integration. For details, see How to Track In-App Events.

   If you have a different attribution tracker/MMP, follow their instructions for reporting events.

2. Then go to Setting > Events and click Add Event. For each event you want to track, give it a name and use the dropdown lists to map it to one or more events reported by your attribution tracker/MMP or offered by self-attributing networks such as Facebook and Google Ads. For other options and settings for defining events, see the following questions.

You may want to track the same type of event across multiple applications. If so, select Global Events and then add the event.

If the event you want to add is only relevant to a specific app, select App-Specific Events and select the app.

In a unique event, you count the number of unique users who did something, e.g., how many distinct users made a purchase (unique event) vs. how many purchases were made through the app (non-unique event).

For example, say you run a report on the date of January 1 with a cohort period of 7 days. This is what occurred for that cohort in that period:

The number of purchases (non-unique) is 4.

The number of unique purchases is 2.

If you choose a date range of more than one day, you are looking at more than one cohort, so the unique events for the different cohorts are simply added up.

For example, running a report on unique purchases in the date range of January 1-10, with the same cohort period, will result in a summary of how many distinct users who installed the app on those days made a purchase within 7 days after installing the app.

Yes, you can map the event to more than one in-app event in the list. For example, if you are defining a cohort event called "sign-up," you can map it to the sign-up event defined in your attribution tracker, and to the sign-up event defined in Facebook.

Check the Cost per Event checkbox to have Singular add a metric that calculates your marketing costs per 1 event of this type (in the same way that Singular measures cost per install).

For example, if you define a "Registration" event, you can have Singular calculate your marketing costs per registration event. The metric will appear in your reports as "Registration CPE."

Check the Event Conversion Rate checkbox to have Singular add a metric that calculates the conversion rate from installs to your event. This is useful if you are optimizing your campaigns toward a certain event.

For example, if you are interested in how many users register to your platform after installing your app, add a "Registration" event, map it to the app's user registration event, and check the Event Conversion Rate checkbox. The Reports page will now include a Registration Conversion Rate metric calculated as registrations divided by installs.

The events you create appear in your query options on the Reports page. The calculated metrics are shown under Cohort Metrics (see What are cohort metrics?).

You can also view event stats through the Singular Reporting API. Use the Cohort Metrics endpoint to retrieve a list of all the cohort events defined in your account. Then, run a report through the Create Async Report endpoint, including one or more of those events.

Yes. Use the Cohort Metrics endpoint to retrieve a list of all the cohort events defined in your account. Then, run a report through the Create Async Report endpoint, including one or more of those events.

You can modify an existing event, with some limitations:

• You can edit the name.
• You can add or remove CPE and ECVR (Event Conversion Rate).
• You can add other events to be mapped to this event, but you cannot remove events that have already been mapped. To remove mapped events, you have to delete the entire event and create a new one from scratch.
• You can't make a unique event non-unique or vice versa.

Conversion events are based on data from your ad networks. Any user interactions that are reported by the network can be used to define a conversion event in Singular.

Choose which events you consider to be "conversions" based on the nature of your product and your goals and KPIs. 

For example:

• If you are marketing an online store, your conversion events could be the user making a purchase or signing up for an account.
• If you're marketing a B2B solution, your conversion event could be a lead (the user asking for a product demo).

Conversion events are based on information from your ad networks. Any user interactions that are reported by the network can be used to define a conversion event in Singular.

To add a new conversion event:

1. Go to Settings > Events and click New Event.
2. Give your event an indicative name and choose what event it maps to in your advertising platform.
3. If you also would also like to see the cost per event calculation in your reports, select the Cost Per Event (CPE) checkbox.
4. Click Save.

Some events, such as purchases and lead creations, are associated with a dollar value. In that case, you can choose if you want your conversion event to track the count of events or the sum of the events' dollar values.

Yes - just define a separate conversion event for each in the Events page.

After you add a conversion event, it is available in the Reports page under "Events," with the name you configured for it.

Event data is also available through the Singular Reporting API. Use the Conversion Metrics endpoint to retrieve a list of all the conversion events defined in your account. Then, run a report through the Create Async Report endpoint including one or more of those events.

You can also view conversion event stats through the Singular Reporting API. Use the Conversion Metrics endpoint to retrieve a list of all the conversion events defined in your account. Then, run a report through the Create Async Report endpoint, including one or more of those events.

Yes - All conversion events which were set up can be added in creative reporting. As long as the network supports the creative granularity you will be able to see stats.

• Conversion events in creatives are only actual and not in cohorts
• We are only displaying network post install events (not tracker)

SKAN events are events measured in SKAdNetwork campaigns. You do not have to define these events manually in the Events page. Instead, they are created automatically for you when you activate an SKAdNetwork conversion model. For more information, see What are SKAN events? [SKAdNetwork Reporting FAQ].

You cannot add or remove SKAN events from the list.

You can rename an event if you want. By default, the event is named after the SDK event that it measures, but you can give it a name that would be clearer to people reading the SKAdNetwork report.

No, no matter how many SKAN events are created through your conversion models, they will not count toward your quota of allowed events.