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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

App SDK implementation: Replace Adobe Analytics processing rules with Launch

Avatar

Avatar
Shape 100
Community Advisor
Andrew_Wathen_
Community Advisor

Likes

592 likes

Total Posts

328 posts

Correct reply

16 solutions
Top badges earned
Shape 100
Bedrock
Coach
Seeker
Contributor 2
View profile

Avatar
Shape 100
Community Advisor
Andrew_Wathen_
Community Advisor

Likes

592 likes

Total Posts

328 posts

Correct reply

16 solutions
Top badges earned
Shape 100
Bedrock
Coach
Seeker
Contributor 2
View profile
Andrew_Wathen_
Community Advisor

02-09-2020

It would be great if in the context of mobile apps, Launch was able to replace Adobe Analytics processing rules.   e.g. allow server side processing of the metrics calls, mapping context data variables to data elements and then mapping data elements to analytics variables using rules, ideally with the ability to execute server side JavaScript to maximise flexibility - all through the launch interface/workflow

 

I was hoping the launch server side road map stuff would deliver this, but is seems to be more about 3rd party integrations/forwarding (or have I got that wrong? 🙂 )

 

 

1 Comment

Avatar

Avatar
Coach
Community Advisor
Andrey_Osadchuk
Community Advisor

Likes

557 likes

Total Posts

1,023 posts

Correct reply

273 solutions
Top badges earned
Coach
Originator
Shape 25
Bedrock
Boost 500
View profile

Avatar
Coach
Community Advisor
Andrey_Osadchuk
Community Advisor

Likes

557 likes

Total Posts

1,023 posts

Correct reply

273 solutions
Top badges earned
Coach
Originator
Shape 25
Bedrock
Boost 500
View profile
Andrey_Osadchuk
Community Advisor

02-09-2020

In addition to this, it would be great if the actual "beacon sent" could be fully controlled in Launch like it works for web. The app should just send data to Launch, but the developer decides whether/when and with what changes (mapping, etc.) to send it to AA (and other destinations).

 

The major inconvenience with apps is that every AA beacon change requires app development. For the website it's much easier as the logic can be configured in Launch itself. It would be great to have a similar flexibility for apps too.