Replies: 2 comments 1 reply
-
ugh, who gave you these values? "ACE0753" is a test number and should no longer be prepended. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Ideally, all our consumers should be using a standardized analytics tracking schema tbh. But I wouldn't be surprised if that's not the case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi All,
We have requirement where we need custom tracking attributes for buttons in a new block in CC. Product (Firefly) team has specific values that they want as daa-ll values.
We are doing that by defining the daa-ll values in the code while creating the elements in js file. So it'll be not standard button text appended by the hyphen and a number.
We also have different daa-ll values if user types in something and then clicks on button or directly clicks on the button.
Here are the analytics values that'll be added as daa-ll for different buttons in the block.
ACE0753:getfirefly
ACE0753:SelectTextToImage
ACE0753:SelectGenerativeFill
ACE0753:SelectTextEffects
ACE0753:SubmitTextToImage
ACE0753:SubmitTextToImageUserContent
ACE0753:SubmitGenerativeFill
ACE0753:SubmitTextEffects
ACE0753:SubmitTextEffectsUserContent
No custom method is written at the block side to generate and send analytics. Only daa-ll values are defined. So the analytics will be tracked like any other block in milo using the functions defined in milo utils file by adding a separator and appending daa-ll and daa-lh values.
Please let us know if you see any issue with customizing the daa-ll values.
cc @vivgoodrich @auniverseaway
Beta Was this translation helpful? Give feedback.
All reactions