Salesforce / Stape sGTM Integration with consent

Google Tag Manager Server Container
1

Hi everyone,

I’m trying to set up a Salesforce integration while handling consent and PII in a privacy-safe way, and I’m unsure what the best architecture would be.

My goal is to send deal status changes e.t.c to advertising platforms via a server-side container (Stape) , while ensuring consent is respected.

I’m currently considering two possible approaches:

Option 1 | Send consent + click IDs with the lead

Steps:

  • Send consent status and click IDs with the lead form submission to Salesforce .
  • Capture the deal status (including PII) from Salesforce in the server container using the Data Client .
  • Trigger conversions based on deal status updates.

Questions:

  • Is this setup possible?
  • In the Stape Conversion Tracking app for Salesforce , can you select custom fields (for example consent status or click IDs)?
  • Is it possible to exclude contacts that do not have consent , so their data is not sent to the server container?

Option 2 | Use Stape ID + Stape Store

  • Send the Stape ID with the lead submission to Salesforce .
  • Store PII and consent information in the Stape Store.(Stape store Writer tag)
  • When the deal status changes, capture the status + Stape ID in the server container via the Data Client .
  • Use Stape Store lookup to retrieve the PII and send the conversion.

Main question

What would be the recommended architecture to implement this safely with consent , while still enabling reliable conversion tracking?

Is one of these approaches best practice, or is there another method that is generally recommended for Salesforce → server-side GTM → ad platform tracking?

Any guidance or examples would be greatly appreciated.

Thanks!

2

Hello!

Both approaches can work. Here’s a quick take on each:

Option 1 is straightforward; store consent status and click IDs in Salesforce with the lead, then capture everything when the deal status changes. Regarding custom fields in the Stape Salesforce app; we need to double-check this internally and will get back to you.

Option 2 is a good alternative if you have limitations on storing custom parameters in Salesforce. You pass a unique identifier with the lead (e.g. Stape ID or email), store consent and click IDs in Stape Store, and look them up when the conversion fires.

One thing to add: for platforms like Google Ads, you can map consent status directly in the offline conversion tags (e.g. ad_user_data, ad_personalization). This works with both approaches.

3

Do you have an update about this (for the record)

4

Hello!

Yes, adding a custom field in the Salesforce app is possible! However, this is something we do after the app has been installed.

If you’d like to move forward or need help getting set up with Salesforce, feel free to reach out to our Sales team directly (kyrylo.hapon@stape.io, oleksandr.pavlenko@stape.io).

Mariia
Stape