I'm seeing a similar problem, but with different nuances, as in this
architect we're working with says that sending cookies from the client
to the server is an anti-pattern, so are there other ways to ensure
sticky experiences? Why does server-side Adobe Target require cookies if
it's an anti-pattern?
I'm sending the trackEvent call and getting a 200 response from the
omtrdc endpoint. However when I check in the Reports dashboard of my
experience, the conversion metric doesn't increment.I double checked
that my conversion mbox is spelled correctly in the trackEvent call, and
I tried with both the "Viewed an mbox" and "Clicked on an mbox"
I want to track clicks on a few elements using a certain CSS selector.
using a for loop to add the trackEvent call to get parameters from the
"my-custom-name" attribute in each selected element. Instead of using
the document.querySelectorAll function to get parameters from the
"my-custom-name" element attribute, is there a way to get those
parameters and send them with the trackEvent call?
How do you get "clicked an mbox" to work? What does "clicked an mbox" do
compared to "viewed an mbox"? I've been adding my own click listener to
the elements I want to track. The event listeners call trackEvents(),
which sends the conversion mbox along with some parameters. This set up
works with "viewed an mbox", but I want to know why it doesn't work with
"clicked an mbox" . Is there some kind of set up in the DOM with the
mbox name that I need to do?I've already looked at the click tracking