# Shared Event Types Explained

Shared event types let you use a single event type, like an online sale, to track actions across multiple programs instead of creating event types for each program. When you mark an event type as shared, it becomes available across all your programs, where you can configure event type commissions or payouts in the program’s template terms.

Shared events award a conversion winner in each program where the shared event is included in a contract. E.g., clicks for a shared event in your Performance and Creator programs would create 2 separate conversion winners and, consequently, 2 separate payouts.

#### Key limitations

* A shared event can only track an activity on one web property, e.g., `www.example.com`.
* Existing brands using a [postback](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/account-settings/notifications/enable-event-notification-postbacks-for-brands) to track across programs should remove the postback before turning on shared events.
* Shared events only work for Performance and Creator program types.
* Shared events do not work with [last-to-cart](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/last-to-cart-credit-policy-explained).
* Mobile event types to track app installs and in-app conversion are not supported.

#### Set up a shared event type

{% hint style="warning" %}
This feature is only available with specific impact.com editions or add-ons. [Contact us](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml) to upgrade your account and get access!
{% endhint %}

The following steps will guide you in identifying a specific event type and marking it as shared.

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1183576591b45997efe4dc81a25024640591d02a%2F245137dc972a7a7f6165b59538fcdbac8fd5bd8fee4ba9f20c1a2982c5b58b57.svg?alt=media) **\[User profile] → Settings**.&#x20;
2. On the right, under *Tracking*, select **Event Types**.
3. On the *Event Type Overview* screen, hover over the event type you want to use in other programs, then select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-8ec3e877b1397045c61d394485e72ac4d93120ee%2Fc6ddb46c637059f06e86c790a911217a9428f5c47b5efef046f90555e85b03cd.svg?alt=media) **\[More]** → **View / Edit**.
4. In the *Shared* section, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-6027673a720a6522269e1861ad0554c4a85baf29%2F9dcf248c757a094c6af27798e61091b8425a0afa1637ae0e5ba3448c5f85b1a1.svg?alt=media) **\[Edit]**, then ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-d0b6669ae76a7bef06a8d6940d7ad5c16bb8d018%2F7cb018d4face8d7cceb880eb5086c812e764fbcfe6f2a0377f88bc7576973070.svg?alt=media) **\[Toggle on] Mark this event type as shared**.
5. Set your shared event type's sharing permissions:
   * Select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-590bdf4e1ffbcc1fe86ad456bebab6a28c64af1f%2Ffd6e4291628446bb1fe27a831f7874b256a28cc84833d72cce2e73b94641edb7.svg?alt=media) **\[Radio button]** **Share with all programs:** This shared event type will become available to all your active programs.
   * Select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-590bdf4e1ffbcc1fe86ad456bebab6a28c64af1f%2Ffd6e4291628446bb1fe27a831f7874b256a28cc84833d72cce2e73b94641edb7.svg?alt=media) **\[Radio button]** **Restrict to specific programs:** Select the programs for which you want to enable this shared event type.
6. Optionally, select the ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[Checkbox]** next to *Single Partner Credit* to only credit one winner across multiple programs using a given shared event type to manage partner payouts when driving conversions.
7. Select **Save**.

<div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FSdZOC1HfYjX9rIJMp4Aw%2FScreenshot%202026-03-10%20at%2011.09.27.png?alt=media&#x26;token=1cccf638-8a1a-446a-91c1-1b76b1a89a00" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
**Note:** The event type you mark as *Shared* will be the main event type you can edit. You are unable to edit the shared event type in any other programs to which it's added.
{% endhint %}

#### Modify template terms using a shared event type

{% hint style="warning" %}
**Important:** To ensure a shared event type takes effect, you must include it in your template terms.
{% endhint %}

1. When [modifying](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/modify-template-terms) or [creating](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms) a template term, navigate to the *Event Type* section and then select your shared event type.
   * Be sure to look for *(Shared)* after the event type name.
2. Continue to modify and save your event type settings.

   * Refer to the [*Event type fields reference*](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms) for more information.

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-f9655b3c5ca2f8c0eb03ae4f3a778316840f6814%2F1fdf27bbc37da223a845592ce264340204857161c60bd3c5a58f3cf226e96478.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### Reverse or modify actions tied to a shared event type

When you send a modification or reversal request, you can use two methods:

* Use an order ID (`OID` )+ event type ID (`ActionTrackerID`) combination: All the other actions that contain the same event type ID will also be reversed or modified.
* Use an `action_id`: Only the unique action will be reversed or modified.

Refer to [batch modifications and reversals file parameters and reason codes](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/batch-modify-conversion-data/batch-modifications-and-reversals-reference) for more information.
