Hi all,
we are currently experiencing strange behavior in the reports from one of our A / B tests.
It's a form-based test where we simply collect the click events of some buttons / links.
Problem: Only two of these are incremented in the reports. The rest only seems to count when we test our JS functions!
(FYI: I don't want to rule out the possibility that we still have a bug in our code)
Has anyone ever had this behavior in general?
All metrics are created in the same way in "Goals & Settings" ("Conversion" & "Viewed an mbox").
The audience is set to "All visitors".
The network queries show that all "trackEvents ()" were triggered and were successful.
Thanks in advance!
Solved! Go to Solution.
Hi @chrish75788707,
Looks like you are using Target as the reporting source. So, the first things I'd check are (and it sounds like you've already checked - but just for others who may see this):
Hope that helps,
Ryan
Hi @chrish75788707,
Looks like you are using Target as the reporting source. So, the first things I'd check are (and it sounds like you've already checked - but just for others who may see this):
Hope that helps,
Ryan
Hello @Ryan_Roberts_,
first of all, many many thanks for your answer and please excuse my late reply.
Yes, we are using Target as a source report.
I will briefly go into the individual points below:
1. Confirmed. The mbox names are exactly as we expect and can also be selected in the "Goals & Settings" via the dropdowns. There are no audience refinements.
2. Confirmed. None of the defined metrics are dependent on others.
3. Confirmed. The conversion requests are fired (checked via the developer console as well as the AEP debugger tool) and the mbox names are as we expect.
4. Confirmed. The environment is set to the production environment and metrics are only counted there. All other surroundings are at 0.
5. (BtW: A very good tip) We copied the activity and checked it again. Unfortunately did not help. We also recreated the activity 1 to 1 again to rule out another error in the configuration, again without success.
We have another source of error in mind that we are currently analyzing. Several different tracking tools are running on the website and there are several other events that are fired on the buttons that are of interest to us. Maybe it's a timing problem or the tools get in each other's way.
If we find out anything, I'll update you guys.
Thank you again for your time and help!
Views
Likes
Replies