Expand my Community achievements bar.

SOLVED

Data Element change Event Type on Purchase Rule

Avatar

Level 4

Hi Team,

 

I have used data element change event type on purchase rule I have used Order_ID data element, but still the rule is not firing. Kindly help, as I am new to launch.

 

bindukumari1990_0-1627383652722.png

 

Note: the duration of data element is none.

1 Accepted Solution

Avatar

Correct answer by
Level 6

First test would be to try out that rule without whatever code you're using for the condition to see if that's what's blocking the rule from firing. So which page is the rule supposed to fire? Checkout, gateway, or confirmation?

Also, as a note, the event "Data Element Change" checks the variable at a frequency of 1 second. So if you are navigating away before the Core extension has an oppertunity to check the values within the data elements, that could be an issue.

View solution in original post

4 Replies

Avatar

Level 6

Hi @bindukumari1990 ,

 

Can you provide context in which the data element is being updated? Is it from within another rule or are you calling _satellite.setVar() directly? It seems more likely that the mechanism setting the variable is failing or the condition on the rule is not met.

Avatar

Level 4

@Jacob-DDdevorder_ID is being updated, in checkout page order_ID is null, so once user is redirected to order confirmation page then order_id is updated and I am calling_satellite.setVar() directly.

 

Note: But before order_confirmation page, payment gateway page comes.

 

 

Avatar

Correct answer by
Level 6

First test would be to try out that rule without whatever code you're using for the condition to see if that's what's blocking the rule from firing. So which page is the rule supposed to fire? Checkout, gateway, or confirmation?

Also, as a note, the event "Data Element Change" checks the variable at a frequency of 1 second. So if you are navigating away before the Core extension has an oppertunity to check the values within the data elements, that could be an issue.

Avatar

Level 6

Also, as a potential solution, since you are calling _satellite.setVar() directly: You can try to put the logic that you are looking for for setting the data element and the variables within a "Direct Call" event type with satellite.track(). This method could avoid some of the timing issues that may arise from the "Data Element Change" event.