Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Adobe Analytics API Bookmark issue

Avatar

Avatar
Validate 1
Level 1
viktorlazar
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
viktorlazar
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
viktorlazar
Level 1

21-11-2017

Hi,

I have a problem with Adobe Analytics API and bookmarks. API behaves very strange and I'm not sure if I'm missing something.
When I test it via Developer Connection API explorer it works as expected and returns the data part of the report
example:

{

    "report":{

        "type":"ranked",

        "elements":[

            {

                "id":"page",

                "name":"Page"

            }

        ],

        "reportSuite":{

            "id":"ams.web.staging",

            "name":"AMS Website Staging Data"

        },

        "period":"2017",

        "metrics":[

            {

                "id":"pageviews",

                "name":"Page Views",

                "type":"number",

                "decimals":0,

                "latency":4363,

                "current":false

            }

        ],

        "data":[

            {

                "name":"name1",

                "url":"url1",

                "counts":[

                    "206"

                ]

            },

            ...

        ],

        "totals":[

            "1355"

        ],

        "version":"1.4.17.2"

    },

    "waitSeconds":0,

    "runSeconds":0

}

If I try this same procedure but from Java code (inside of AEM) result is missing the data part.
example:

{

    "report":{

        "type":"ranked",

        "reportSuite":{

            "id":"ams.web.staging",

            "name":"AMS Website Staging Data"

        },

        "period":"2017",

        "elements":[

            {

                "id":"page",

                "name":"Page"

            }

        ],

        "metrics":[

            {

                "id":"pageviews",

                "name":"Page Views",

                "type":"number",

                "decimals":0,

                "latency":4265,

                "current":false

            }

        ],

        "data":[

           

        ],

        "totals":[

            "1355"

        ],

        "version":"1.4.17.2"

    },

    "waitSeconds":0,

    "runSeconds":0

}

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
Employee
Gigazelle
Employee

Likes

470 likes

Total Posts

1,947 posts

Correct Reply

739 solutions
Top badges earned
Coach
Contributor 2
Validate 1
Ignite 80
Ignite 70
View profile

Avatar
Coach
Employee
Gigazelle
Employee

Likes

470 likes

Total Posts

1,947 posts

Correct Reply

739 solutions
Top badges earned
Coach
Contributor 2
Validate 1
Ignite 80
Ignite 70
View profile
Gigazelle
Employee

28-11-2017

Hi Viktor, that sounds like a bug. If you could have a Supported user contact Customer Care, we can do some more in-depth research on what's going on and potentially provide a fix. Thanks!

Answers (0)