We suspect that Adobe SDK is doubling our unique visitors for one of our Mobile App | Community
Skip to main content
V
venukam82699228
Level 2
August 12, 2021
Solved

We suspect that Adobe SDK is doubling our unique visitors for one of our Mobile App

  • August 12, 2021
  • 1 reply
  • 1162 views

 

The number of unique visitors per month are making sense when the unspecified value is added with the # of unique visitors on the dashboard landing page. This led us to suspect that Adobe SDK might be doubling the value and the users are counted separately with the Lifecyle call. 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by VaniBhemarasetty

@venukam82699228 It would be difficult to comment on the root cause for this issue, you might have share the logs, config.json and implementation details and raise a ticket with client care adobe to resolve this issue.

1 reply

VaniBhemarasetty
Adobe Employee
VaniBhemarasettyAdobe Employee
Adobe Employee
August 13, 2021

@venukam82699228 You can check the logs like charles logs or any other third party tool to see if the MID or visitor ID changes for the same visitor. If you are suspecting that unique visitors are incrementing when lifecycle metrics are set or when app is launched, check the logs and see if the visitor ID changes for a single user for these respective actions.

That would confirm unique visitors are getting incremented or not

    V
    venukam82699228Author
    Level 2
    August 13, 2021

    Thank you for the input @vanibhemarasetty . Yes, I could see two different mid id values on Charles for the app in one session. The mid value on lifecycle call and the smetric call are two different values. Do you know how to fix this?

    VaniBhemarasetty
    Adobe Employee
    VaniBhemarasettyAdobe EmployeeAccepted solution
    Adobe Employee
    August 14, 2021

    @venukam82699228 It would be difficult to comment on the root cause for this issue, you might have share the logs, config.json and implementation details and raise a ticket with client care adobe to resolve this issue.

    Terms & ConditionsAccessibility statement

    Loading footer...