Skip to main content
Attributes for Pixels and S2S Events

How to enable advanced integration features like predictive audiences and server-to-server connections for Meta/Facebook and Outbrain. How to configure conversion pixels by adding specific attributes to script tags.

Admetrics avatar
Written by Admetrics
Updated over 2 months ago

Attributes for Pixels and S2S Events

To enable advanced integration features such as predictive audiences and server-to-server (S2S) connections for platforms like Meta/Facebook and Outbrain, you need to add specific attributes to your script tags.

⚠ Note: This is only required for manual pixel installation, such as on custom shops or landing pages. For most clients using standard eCommerce platforms, this setup is handled automatically.

These attributes allow you to:

  • Configure conversion pixels for Meta, TikTok, and other vendors.

  • Activate predictive audience targeting, ensuring ads reach the most relevant users.

  • Enable server-to-server (S2S) connections, which improve tracking accuracy by sending data directly from our servers instead of relying on browser-based tracking.

By adding the right attributes to your script tags, you can seamlessly integrate these features and optimize your campaign performance.

data-pa-vendor

Enables Predictive Audiences for specific vendors. When enabled, the pixel will send admetrics_intent events to the selected vendors.

  • Format: Comma-separated list of vendors

  • Allowed values:

    • fb (for Facebook/Meta)

    • google

  • Example: data-pa-vendor="fb,google"

  • Extended example:

 <script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-pa-vendor="fb,google"
></script>

data-pa-mpid

Specifies Facebook/Meta pixel IDs for Predictive Audiences.

  • Format: Comma-separated list of IDs

  • Example: data-pa-mpid="123,456"

  • Extended example:

 <script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-pa-mpid="123,456"
></script>

data-ss-mpid

Specifies Facebook/Meta S2S pixel IDs.

  • Format: Comma-separated list of IDs

  • Example: data-ss-mpid="123,456"

  • Extended example:

<script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-ss-mpid="123,456"
></script>

data-ss-tkpid

Specifies TikTok S2S pixel IDs.

  • Format: Comma-separated list of IDs

  • Example: data-ss-tkpid="123,456"

  • Extended example:

<script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-ss-tkpid="123,456"
></script>

data-ss-scpid

Specifies Snapchat S2S pixel IDs.

  • Format: Comma-separated list of IDs

  • Example: data-ss-scpid="123,456"

  • Extended example:

<script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-ss-scpid="123,456"
></script>

data-ss-ob

Enables Outbrain S2S events.

  • Format: Single value

  • Allowed value: "1" to enable

  • Example: data-ss-ob="1"

  • Extended example:

<script id="js-app-admq-script"
src="https://shopify.admetrics.events/conversion-v1.min.js"

data-ss-ob="1"
></script>
Did this answer your question?