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

Launch Environment - Async always on

Avatar

Avatar
Validate 25
Level 4
scottt6073095
Level 4

Likes

66 likes

Total Posts

102 posts

Correct Reply

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

Avatar
Validate 25
Level 4
scottt6073095
Level 4

Likes

66 likes

Total Posts

102 posts

Correct Reply

3 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 50
Boost 5
View profile
scottt6073095
Level 4

24-05-2018

Hi All,

I was wondering if anyone else is having the same issue. I went into my Environments and they are all set on async and when I go to turn off async and save it I go back into the specific environment and its turned on again. Is this a glitch or should I not worry about it.

Also, what are all the pros and cons of using async?

Pros:

  • non-blocking
  • faster performance

Cons:

  • Adobe Target; experience personalization
  • Don't use page bottom event type

1493696_pastedImage_2.png

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Springboard
MVP
StewSchilling
MVP

Likes

339 likes

Total Posts

276 posts

Correct Reply

85 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Establish
Contributor
View profile

Avatar
Springboard
MVP
StewSchilling
MVP

Likes

339 likes

Total Posts

276 posts

Correct Reply

85 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Establish
Contributor
View profile
StewSchilling
MVP

24-05-2018

I see the same thing.  My guess is that they want to encourage async deployment as the default best practice (A stance with which I happen to agree).

I am also pretty much in agreement with your list of pros and cons. 

The point about _satellite.pageBottom() is a little nuanced though.  My understanding is that you _could_ write rules that fire when _satellite.pageBottom() is called, but with an asynchronous embed of the header code, you don't have any guarantee that the _satellite object will be in existence by the time that the footer embed is rendered.  I can't really think of a reason why you'd call _satellite.pageBottom() outside of its intention as a marker of the bottom of the body being hit, but maybe it will come in handy some day...

It is also my understanding that the Launch library itself is no different if you choose synchronous or asynchronous deployment.

Answers (8)

Answers (8)

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

24-05-2018

You should not worry about it.  Those are deployment instructions, they are not a setting that is connected to how you actually deploy it.  And we did recently change it to show async by default (we are encouraging people to make that move), but it's still just instructions.

You have Target on your Cons list, I don't think it belongs there.  Launch supports asynchronous deploys of Target.  With a little effort outside of Launch you can also do it without any flicker (instructions here).

The Launch Library is the same whether you choose to deploy it sync or async.

Finally, _satellite.pageBottom is essentially just a Direct Call with a special name.  And in async deploy scenarios you should not be building rules to fire on Page Bottom since the timing is unknowable and unreliable in async deploys.  You can still use it (and if you do, Launch will string things together in their logical order), but the timing will be messed up and it's not recommended.

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

22-03-2019

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

11-11-2019

Thanks, updated the link above 😃

Avatar

Avatar
Boost 5
Employee
apowersadobe
Employee

Likes

6 likes

Total Posts

9 posts

Correct Reply

4 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile

Avatar
Boost 5
Employee
apowersadobe
Employee

Likes

6 likes

Total Posts

9 posts

Correct Reply

4 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile
apowersadobe
Employee

10-11-2019

Another link update:

Adobe Target extension

Avatar

Avatar
Validate 1
Level 1
bharathn7761115
Level 1

Like

1 like

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
bharathn7761115
Level 1

Like

1 like

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
bharathn7761115
Level 1

22-03-2019

Looks like the link you have provided to handle the flicker in Target is expired. It would be great if you can post the updated link.

Thanks

Bharath

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

140 likes

Total Posts

312 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

19-07-2018

The unsatisfying answer is that it depends on your use cases.  On the product team, we use "Library Loaded - Page Top" for all our basic demos.

Avatar

Avatar
Level 1
adls_vlaba19774
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
adls_vlaba19774
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
adls_vlaba19774
Level 1

27-06-2018

So what is the best practice event to use for a General / All Pages Rule with Launch? The new Launch training has a Page Load - Page Bottom event - Which Page Load event would you consider best practice to use when selecting to load asynchronous?

Avatar

Avatar
Validate 25
Level 4
scottt6073095
Level 4

Likes

66 likes

Total Posts

102 posts

Correct Reply

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

Avatar
Validate 25
Level 4
scottt6073095
Level 4

Likes

66 likes

Total Posts

102 posts

Correct Reply

3 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 50
Boost 5
View profile
scottt6073095
Level 4

24-05-2018

In regards to Target, Glad to hear that it's not a con as we will be implementing it in a few months. and thanks for the link to the target doc.