Using Web SDK consent queueing | Community
Skip to main content
SSampsa
SSampsa
Level 4
May 27, 2025
Solved

Using Web SDK consent queueing

  • May 27, 2025
  • 1 reply
  • 675 views

Within Adobe Tags, when setting up the Web SDK extension, we have default options for consent. Three default models (in, out and pending) as well as a configurable object to configure with more in-depth level.

My question is regarding the "pending" option, which is stated to queue the calls until user gives consent and then act based on consent given, either by sending calls with opt-in or discarding them with opt-out.

 

The issue I'm facing that regardless of if I use the default "pending" option, or define a custom consent object that uses the pending values, calls triggered before opt-in and should be queued are never sent. Is this expected behavior or am I missing something?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Parvesh_Parmar

 

Hi @ssampsa ,

 

I found the following documentation that might be helpful:

 

 

 

If I understand it correctly:

Even when the Web SDK defaultConsent is set to "pending"—either by default or through a custom consent object—

defaultConsent: "pending"

 

  • Events (like sendEvent) triggered before consent is granted should not be sent immediately.

  • They should be queued and only sent after setConsent indicates opt-in.

  • If opt-out is given, queued events should be discarded.

 

 

Kind regards,

Parvesh

 

1 reply

Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity AdvisorAccepted solution
Community Advisor
May 27, 2025

 

Hi @ssampsa ,

 

I found the following documentation that might be helpful:

 

 

 

If I understand it correctly:

Even when the Web SDK defaultConsent is set to "pending"—either by default or through a custom consent object—

defaultConsent: "pending"

 

  • Events (like sendEvent) triggered before consent is granted should not be sent immediately.

  • They should be queued and only sent after setConsent indicates opt-in.

  • If opt-out is given, queued events should be discarded.

 

 

Kind regards,

Parvesh

 

Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
    SSampsa
    SSampsaAuthor
    Level 4
    May 28, 2025

    Hey Parvesh and thank you for the answer. 


    I have been looking at the same documentation and the model on how consent is supposed to work. The issue is that even as I set consent to be "pending" and then later opt-in, calls that were supposed to be queued are not set, but rather just discarded.

     

    Expected behavior:

    1. Load site, consent set to "pending"
    2. Page call triggered, queued due to consent
    3. Consent given
    4. Queued call sent

    Actual behavior:

    1. Load site, consent set to "pending"
    2. Page call triggered, queued due to consent
    3. Consent given
    4. Previously queued calls are not sent

    There is no page load between queued calls and I've confirmed the consent is set correctly, using Adobe's consent model 2.0.

    Parvesh_Parmar
    Community Advisor
    Parvesh_ParmarCommunity Advisor
    Community Advisor
    May 28, 2025

    Hi @ssampsa ,

     

    I agree with you — it’s not working as expected in your case.

    Sometimes, certain information might be missing or not fully defined in the documentation, especially when there are dependencies on other components.

    In such cases, I usually contact Adobe Support and explain that I’ve implemented everything as per the documentation. I also include screenshots, documentation links, and any relevant details.

    They are generally quite responsive, so you might consider reaching out to them as well.

    Kind regards,
    Parvesh

    Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
      Terms & ConditionsAccessibility statement

      Loading footer...