Hi!
We are currently using Adobe Target for testing in a complex environment from a technical perspective so the majority of our test are "developed" through custom code
This implies developers manipulate html + js + css code "by hand" in all of the lifecycle (analysis, development, validating, deploy to production) and we want to implement some version control system to this workflow, specifically git, to make it safer and to comply some internal regulations
So here are my questions:
Thanks
Solved! Go to Solution.
Hi @HugoNebreda
Judging from what you described, our situation is also quite similar. We use a build app to compile our separate HTML, CSS and JS and perform any functions to make it Adobe Target offer compatible (e.g. reusing popular tracking functions etc).
We'd recommend using your current source control system (we use Bitbucket) and then as part of the build process, send the compiled code to Adobe Target via the Target API as 'offers'
Hi @HugoNebreda
Judging from what you described, our situation is also quite similar. We use a build app to compile our separate HTML, CSS and JS and perform any functions to make it Adobe Target offer compatible (e.g. reusing popular tracking functions etc).
We'd recommend using your current source control system (we use Bitbucket) and then as part of the build process, send the compiled code to Adobe Target via the Target API as 'offers'
Views
Like
Replies