Automated Personalization Form Based Experience Composer

Avatar

Avatar
Validate 1
Level 2
nmickley
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
nmickley
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
nmickley
Level 2

13-03-2017

Hi Everyone,

Wondering if anyone has heard if the Form Base Experience Composer will be added to Automated Personalization.

We're shifting away from inline mbox calls toward the API to improve our site performance. The visual composer does not allow us to do this well.

Thanks!

Nick

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

93 likes

Total Posts

817 posts

Correct reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

93 likes

Total Posts

817 posts

Correct reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile
ParitMittal
Level 10

14-03-2017

Hi Nick ,

 "Form-Based Composer for AP" is on the Adobe Target Future Roadmap However We are not sure of the date / timeline on when it will be available to the Adobe target Users.

Also,The at.js library is a new implementation library for Adobe Target designed for both typical web implementations and single-page applications.

Among other benefits, at.js improves page-load times for web implementations and provides better implementation options for single-page applications.

The at.js library offers several improvements over the mbox.js library, including:

  •   Completely asynchronous communication via cross domain AJAX
  •  Important: Although at.js communicates with the Target servers asynchronously, the at.js file itself must load synchronously in the <head> section of your page. Ideally, it should be one of the first scripts loaded. Once loaded, at.js executes mbox calls asynchronously through XMLHttpRequest, and does not block page rendering.
  •  No more blocking calls
  •  No document.write() used
  •  No immediate execution of JavaScript in Target responses
  •  Better timeout and error handling
  •  Customizable timeout per call
  •  No reloads on timeouts
  •  Functions designed specifically for single-page apps/MVC frameworks

Please see the following link for more info : https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-atjs-implementation.html

Thanks

Parit Mittal

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 2
nmickley
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
nmickley
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
nmickley
Level 2

14-03-2017

Hi Parit,

Thank you for your response. Yes, we are using mbox.js. We will be switching to at.js sometime this year, though. Is one better than the other?

Thanks,

Nick

Avatar

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

93 likes

Total Posts

817 posts

Correct reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

93 likes

Total Posts

817 posts

Correct reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile
ParitMittal
Level 10

13-03-2017

Hi Nick,

Are you using at.js or mbox.js for Adobe Target implementation ?

Thanks & Regards

Parit Mittal