Open gbenitMC opened 10 months ago
hi @gbenitMC I apologise for the slow reply. I had missed the notification. Have you solved the problem since you posted ot should I look into it?
Hello,
No problem at all for the delay, thank you for your time and get back to me.
I still have the issue, I'd be willing to present the issues to you in a call so that you can see them more clearly.
Best,
Gabriel BENIT UX Designer
@.*** 25 rue de Galeben - 33380 Mios
[https://storage.letsignit.com/5b2a1ddaa0cae50005038fa0/logo_5b2a1ddaa0cae50005038fa0_1916a33a6a1b4c1e6263e0f8a65f9100_5dfa27dad7c38e000aba6469_346471755dc4108e6b0138385b79ddaa.png]https://cloud.letsignit.com/collect/bc/5dfa27dad7c38e000aba6469?p=5JtAdCshLH8Pi3XWPQdS4USM7XYow5wSfeWH39O4dBdS81qojLsqteOZTEGT3KSece29dqhtik7VPljKOP81ouU_z5ON46A5aOWtw6zRNVx2l3Ndy4CLpvBQpRzgvh4VEJ_vdwln_1HDDTCc0PKJiw==
|
De : Rob Freeman @.> Envoyé : jeudi 25 janvier 2024 10:23 À : adobe/reactor-extension-googledatalayer @.> Cc : Gabriel BENIT @.>; Mention @.> Objet : Re: [adobe/reactor-extension-googledatalayer] Event visibility wrong data associated (Issue #33)
hi @gbenitMChttps://github.com/gbenitMC I apologise for the slow reply. I had missed the notification. Have you solved the problem since you posted ot should I look into it?
— Reply to this email directly, view it on GitHubhttps://github.com/adobe/reactor-extension-googledatalayer/issues/33#issuecomment-1909732378, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2OUC3INTAMJU6URO7KXRA3YQIQAHAVCNFSM6AAAAABBRTM752VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZG4ZTEMZXHA. You are receiving this because you were mentioned.Message ID: @.***>
had a call with @gbenitMC . Workaround found (use standard Launch event object in action, rather than data element (event.event....). Bug is why the Data Element is not behaving in the same way as the event object. Product bug?
hey @gbenitMC , could you try something for me please. Use the trouble dataelement in an action where it can be included with {{dataElement}}. You could for example use the GDL extension key-value push action. Please then let me know if the values that are pushed (or some other extension action) are correct.
hey @gbenitMC , could you try something for me please. Use the trouble dataelement in an action where it can be included with {{dataElement}}. You could for example use the GDL extension key-value push action. Please then let me know if the values that are pushed (or some other extension action) are correct.
Hello @brobatr ,
So with the GTM visibility element I have this object:
Just to know what precisely should I put in the console.log:
Could you describe me, if I understand well, what value I should precised in a DataElement var (Google Data Layer property):
and then put into the console.log?
Because in the visiblity object I don't see where is the "extension key-value push action"?
Thank you in advance!
hi @gbenitMC , I mean please add an action to the rule after your console log statement. You can use anything that takes a dataElement variable in %myDataElement% (I was wrong in my last message with {{}}). An example would the WebSDK extension send action, or the action below from the GDL extension
In this case you check your datalayer after page load so see if you have a series of 'test' entries with the gtm.element element links
@brobatr
All the details asked in screenshots, do not hesitate if you need something more or if I miss something.
Hello,
I'm taking the liberty of contacting you because I use your plugin, which is a real time-saver for the transition from GTM to Adobe Launch, so first of all I'd like to thank you enormously for the work you've done.
https://exchange.adobe.com/apps/ec/108445/google-data-layer
I do, however, have a slight comprehension block when using it. I want to retrieve my "gtm.elementVisibility" GTM events.
However, I have a number of visibilities that can be sent in quick succession if several elements on the screen are displayed side by side simultaneously.
And I have the impression that the content retrieved from the datalayer is not the right one, because the same information is retrieved several times instead of taking each visibility trigger individually.
Below are two screenshots. The first shows the contents of my datalayer. The second shows the rendering of my rule running on the adobe side.
This problem only occurs when visibilities are sent with the "page load".
(my visibilities are sent each time they appear on the screen) When I go over them a second time, they have the expected content:
I tried searching the GitHub but couldn't find a similar case.
My console.log code is based on the following elements:
So it seems that the gtm.element content doesn't loop over all gtm.visibility events and retrieve information 1 by 1 when this follows direct page loading.
Have you ever encountered a similar scenario? It's possible that I've misconfigured it too, so don't hesitate to let me know if you need anything more specific. I can be available for a quick demo call.
Thank you in advance for your help and your time.
Benit Gabriel UX Designer and Data Consultant in France