Gatsby Data Element in Adobe Launch

I know nothing about gatsby so cant be a definitive guide here.

In a nutshell you need to check for each page(virtual page if its a Single page  App) that you get an adobe beacon. You may need to add logic such that on those pages where it doesn't fire as expected you do something like a direct call rule to fire your Adobe tag.

You can use network tab in browser. Filter to see parameters tab use filter of "/b/ss/ and check if beacon fires as expected.

Hey Hi @warrensassoon 

As you said it's not fire on all pages however it's fire on some pages do you see any differences between these two - I would suggest to check in console or network tab. 

other thing I noticed in screenshot as you selected storage duration as PageView - Do you want to hold this value in each case? 

You have below choices available so check which is suitable for your requirement 

The available choices are:

• None
  • The value is not stored.
• Page view

  • The value is held in a JavaScript variable until the page is refreshed or a new page is loaded.

  • Can be created and set in scripts using _satellite object syntax:

    _satellite.setVar('data_element_name')

• Session
  • Values persist in the browser’s session storage until the browser tab is closed.
  • Available throughout the site visit.
• Visitor
  • The value is stored indefinitely in the browser’s local storage.

Hope this helps

While this data element might be a culprit, I think you also want to check the Rule(s) that send your AA beacon. It could be that they have conditions that no longer match how your website works, so that's why the beacons are not being sent to AA for some pages.