Custom (Page View) Event and Purchase | Community
Skip to main content
R
Rafael_Sahagun
Level 3
February 13, 2025
Solved

Custom (Page View) Event and Purchase

  • February 13, 2025
  • 1 reply
  • 971 views

Hello.

Adding a custom event for page view is suggested so it can be used with eVars as I understand.

Does that cause an issue when firing alongside purchase on purchase page? should it be omitted in certain steps or all events can fire anywhere?

The main issue we have is that a numeric event is not being sent in all purchases where it should.

Also is not an event that fires in the data layer, instead a data layer property that later is setup as an event.

Thanks!

R

 

Best answer by Jennifer_Dungan

You can fire custom events as you need.. on page view or actions, you can fire as many as you need for your specific purposes.

 

So, if you are trying to make you own replication Page View event (which by the way, you can use the standard page view event with eVars as well), then I would trigger it on all "page view actions"... if your purchase success is tracked on the page (and not as a separate action), then I would fire both "eventX,purchase" on that particular page view.

 

 

The implementation of this will be driven by your logic and needs, but there is nothing wrong with having something that looks like:

 

s.events = "event1,event2,event3=5,event4=5.00,purchase"; s.products = "Example category;Example product;5;1.00;event2=1;eVar1=Example merchandising value 1|eVar2=Example merchandising value 2";

 

event1 is a global counter, event2 is your numeric merchandising event, event3 is a total product count, event4 is the current purchase total and then the purchase event.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 13, 2025

You can fire custom events as you need.. on page view or actions, you can fire as many as you need for your specific purposes.

 

So, if you are trying to make you own replication Page View event (which by the way, you can use the standard page view event with eVars as well), then I would trigger it on all "page view actions"... if your purchase success is tracked on the page (and not as a separate action), then I would fire both "eventX,purchase" on that particular page view.

 

 

The implementation of this will be driven by your logic and needs, but there is nothing wrong with having something that looks like:

 

s.events = "event1,event2,event3=5,event4=5.00,purchase"; s.products = "Example category;Example product;5;1.00;event2=1;eVar1=Example merchandising value 1|eVar2=Example merchandising value 2";

 

event1 is a global counter, event2 is your numeric merchandising event, event3 is a total product count, event4 is the current purchase total and then the purchase event.

    R
    Rafael_SahagunAuthor
    Level 3
    February 14, 2025

    Thanks @jennifer_dungan for the detail.

    I forgot to mention this is web sdk/xdm implementation, but your example can be adapted to xdm.

    All works ok except a numeric event that should add the number of coupons used in the transaction.

    I don't have access to make changes or test but the admin thinks because he is firing the custom page view alongside purchase event (which fires its own pageview) is forcing a duplicate pageview and messing things up.

    For now he is removing the custom pv and just firing purchase.

    From what I understand, firing a custom event alongside purchase shouldn't be an issue and should look elsewhere for solutions.

     

     

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      February 14, 2025

      Yeah, my example was just showing a mix of different events all being used together (and yes, this would work with WebSDK/XDM Streams too, just a slightly different format)...

       

      Now, if your developer isn't properly stitching the events onto the same tracking call, then yes, you will have a problem.... while one of those calls can be a page view and the other can be an action, you won't be able to properly correlate information between the two calls (or at least not without a lot of work) and you will be increasing costs due to additional (and unnecessary) server calls. If both calls are Page Views, you are inflating PVs...

       

      You will have to work to find a proper solution to conjoin the two tracking calls into the same call for better data consistency and ensuring server call efficiency.

        Terms & ConditionsAccessibility statement

        Loading footer...