Thanks @analytics_union So considering I've 3 seperate FB pixel ID from 3 different media agency which we deal with like ABC="123456", PQR="123456", XYZ="123456" In this case how the data element pass to FB extension will work. Any idea? Thanks in advance. Appriciate your help.

Re: Pass multiple account / pixel ID to Facebook launch extension gokula - Adobe Experience Platform Launch

Thank you for quick response @analytics_union . So do you mean when we configure new FB account ID in data element which overwrite on the account ID already configured in FB extension.

Re: Pass multiple account / pixel ID to Facebook launch extension gokula - Adobe Experience Platform Launch

Hi everyone, Any one came across this situation - tagging few members here to just get help for this post@analytics_union @Andrey_Osadchuk @PratheepArunRaj

Re: DTM to Launch : Use of private extensions with migrat... gokula - Adobe Experience Platform Launch

Hi @Judicaël_Ihorim I've had came to same situation earlier. Technically speacking there is no alternative when you migrate the properties from DTM to Launch. The "development" flag only available at the time of creation of new property. But yes there is other alternative I've tried. You can create new development property for your private extension and then once you installed private extension in newly development property - the same extension will be available in other properties too respectiv...

Pass multiple account / pixel ID to Facebook launch extension gokula - Adobe Experience Platform Launch

Hello Team, We are using Facebook pixel extension to measure the effectiveness of advertising by understanding the actions. Currently we are working with different agencies who provide us different ID's. The current Facebook extension accepts only one ID so I'm looking it to customise Facebook extension which accetps multiple ID's and make new develop extension. I'm referring to example https://github.com/Adobe-Marketing-Cloud-Activation/extension-facebookpixelbut Have you ever come across this ...

Re: Adobe Experience Platform Web SDK gokula - Adobe Experience Platform Launch

Thanks @justin_grover. This is really helpful

Adobe Experience Platform Web SDK gokula - Adobe Experience Platform Launch

Hello Team, Has anyone recently implement AEP Web SDK ( Project name Alloy). Interesting to know the steps to get it done and how to replace AppMeasurement.js, Visitor.js, and AT.js with one tag to rule them all.

A property is in a republished state notification must be belongs to the property where the library republished gokula - Adobe Experience Platform Launch

Hello Team, Currently we're seeing the republished state notification in different property where the republished library not exist. So its better to show the notification where it belongs to. For example. Look at the below screenshot. The republished library AppD belongs to different property but I can able to see the republished notification in above property where AppD Fixes library not exist at all. Looks like its a Launch UI bug - but if it's not considered while implementation so sharing t...

Adobe Experience Platform Web SDK - AEP Web SDK Launch extension gokula - Adobe Experience Platform Launch

Hello Team, Has anyone recently implement AEP Web SDK Launch extension? Interesting to know the steps to get it done and how to replace AppMeasurement.js, Visitor.js, and AT.js with one tag to rule them all.

Re: Someone please share the URL for identity services us... gokula - Adobe Experience Platform

Hi, I think ECID is the client side module providing access to identity management. Explore the more resources here https://docs.adobe.com/content/help/en/id-service/using/home.html

Re: DTM to Launch Migration (Staging Library) gokula - Adobe Experience Platform

Hi The DTM staging library does not linked with Launch staging. Both are different. It's up to you, if you really want to replace the DTM staging embed code with Launch staging code. Ultimately, once you're fully migrated to Launch, the DTM staging embed code not work at all until you disabled the DTM property. You can achieve in simulation way and load the Launch staging functionality in browser with the help of Adobe experience cloud debugger, Go to Tools -> replace the Launch embed code with ...

Re: Build date issue - if library has been republished gokula - Adobe Experience Platform Launch

even I republished again, the date issue is still there. Launch not showing the republished date and taking the original library only.

Re: PDF tracking in Adobe Launch gokula - Adobe Experience Platform Launch

Yes but its only used for the URL / links which having the .pdf as extension but not works for the URL which open as pdf without pdf extension

Re: Launch embed code vs DTM embed code gokula - Adobe Experience Platform Launch

Yes, If you want to swap DTM embed code with Launch directly at page level you can do that. Only make sure don't push any changes through DTM if the DTM property still in active mode after migration. Better disabled that property after complete migration into Launch.

Re: Build date issue - if library has been republished gokula - Adobe Experience Platform Launch

No nothing worked for me. Satellite still shows the buildDate of the library originally published.

Re: Build date issue - if library has been republished gokula - Adobe Experience Platform Launch

I just went through Release notes of Launch and found that this was bug which fixed on January 16,2020 but here in my case I can see this bug not fixed. Here is the Bug reference https://docs.adobe.com/content/help/en/launch/using/intro/release-notes/current.html Bug FixesThe republish library feature would sometimes not purge the Launch asset on Akamai properly and result in the original library still being served. @thebenrobb @StewSchilling

Build date issue - if library has been republished gokula - Adobe Experience Platform Launch

Hello Team, In our current Launch implementation we have republished the library but when we check in browser console using satellite.buildInfo command, showing the build date when the library originally published. Sometime this varies so not sure what happening exactly. Is there any issue with Launch ? For reference please see attached screenshot.

Fire adobe launch extension on Specific page rather than every page gokula - Adobe Experience Platform Launch

Hello Team, Is there any way where I can fire the extension on specific pages only and not on every page. For ex. Adobe Target v2 extension loaded on every page which adds chunk of JS code on every page even though the page doesn't have any experience loaded. This adds into main JavaScript file and had a major impact on our site page performance comparing to DTM. @jenn_kunz1 @StewSchilling

PDF tracking in Adobe Launch gokula - Adobe Experience Platform Launch

Hello team, we have requirement of PDF tracking where few links with pdf extension and few are without pdf extension like below https://www.abc.com/abc-pqr/view.cgi?f=223388.pdf https://www.abc.com/abc/pqr-xyz/travel/australia.pdfhttps://www.abc.com/abc/pqr-xyz/travel This URL are auto redirect where PDF download. If I want to implement custom event tracking to know how many clicks for pdf download what are the option.

Re: JavaScript error with at.js 2.1.1 gokula - Adobe Target

Hi Surebee - No increasing the timeout still showing the error in Prod which is really matter of concern for us. Same thing for Disabled opt out error. I'll raise the client care ticket with P1. Thank you.

Re: JavaScript error with at.js 2.1.1 gokula - Adobe Target

Hi Surebee, Yes, Visitor API timeout default only. visitorApiTimeout: 2e3, but after your above reply, I just thought to add in custom way like below window.targetGlobalSettings = { visitorApiTimeout: 3000 // using custom API timeout };About Disabled due to opt out - It's just showing in the at.js 2.1.1 Not sure from where is getting triggered.

Re: JavaScript error with at.js 2.1.1 gokula - Adobe Target

Hi Surebee,Is both configuration mandatory? we haven't set any custom configurations. We've just followed the document Upgrading from at.js 1.x to at.js 2.x and implemented and upgraded the library month's ago. I have not seen Adobe specifically mentioned about above configurations and we had issues with up-gradation too that time we raised the client care ticket and solved the issue but even client care not communicate about these configurationsDo I need to implement these things as custom way?...

Re: JavaScript error with at.js 2.1.1 gokula - Adobe Target

Hi ShruthiThanks for the reply. I'm afraid, you can't see the errors in console, as these errors getting logged in our AppDynamics tools. I can share the log's with you which comes with URL. Do you want me to share the log's here? I mainly find it strange that these are occurring as errors on the page – it feels like something that should fail a bit more silently.My concern is .. Is it something we missed in our configuration / implementation or Is Adobe already aware of these error's and waitin...

JavaScript errors - Disabled due to opt-out gokula - Adobe Experience Cloud

Hello Team,we’re logging the following JavaScript errors on our site.Disabled due to opt-out How can we resolved that? Is is some thing coming from Adobe Experience cloud ID service? Thanks,

JavaScript error with at.js 2.1.1 gokula - Adobe Target

Hello Team, we’re logging the following JavaScript errors on our site. Visitor API requests timed out (approx. 130 errors per day)Disabled due to opt-out” (approx. 400 errors per day) These both appear to be coming from the Adobe Target at.js library 2.1.1. @How can we resolved that? Is there any configuration needed. Thanks,jantzen.belliston-AdobeAmelia Waliany

Add the ability to have metadata for the Launch property, Rules, DataElements, Extension gokula - Adobe Experience Platform Launch

Hello Team, Can we have the ability to add metadata for the Property, rules, datalements, extension so that we can get to know easily who create it, what's the purpose, under which category the rules, datalement resides. It would be great to know this things to avoid redundancy. This feature have in DTM at the moment and with the help of metadata we can search the things easily. Currently in the list of all properties, I'm not able to see who created that property? when it's published last time ...

Re: Additional Analytics Instances in Launch Extension gokula - Adobe Experience Platform Launch

Andrey Osadchuk jantzen.belliston-AdobeHi both, We do have the same situation. In DTM, we used to have two analytics tool but as this is not possible in Launch .. I came up with below. In case if any different ideas you have please suggest. "we’ll go ahead with page load rule containing all the app measurement code and custom code for our partner analytics tool and then we triggered this rule once after our own analytics image request fired using rule ordering. As rule ordering allows us to co...

Re: Activity is not getting publish in Adobe's Delivery network gokula - Adobe Target

Hey @rizwanuli19780461Last week only I've experienced the same issue and tried below solutions. You can check if anything works for you.before came to these solutions - I searched a lot on Google, in Adobe forums, Adobe target documentation but not seen any fruitful solution and even not understand why it's occurring. If someone can tell us the root cause then that really appreciated Solutions-1) check if there is any syntax error in code.2) Try to clear the cache cookies from the browser

at.js 2.1.1 with remote offers not working. gokula - Adobe Target

Hello Team,I'm using the latest version of at.js 2.1.1 but facing issues with remote offers? I've set up the test experience using forms-based composer and injecting the image content in the mbox location. mbox is hardcoded in the page like below. if (typeof adobe === 'object' && typeof adobe.target === 'object') { adobe.target.getOffer({ "mbox": "mbox_name", "success": function(offer) { console.log("mbox_name_offer_name", offer); adobe.target.applyOffer({ "mbox": "mbox_name", "offer": offer }); }, "error": function(status, error) { console.log('Error - status', status); console.log('Error - error', error); } }); }Using Activity QA, I'm using the URL generated by Target for viewing the variations like for Experience A ?at_preview_token=xxxxxxxxxxxxxxx8%xxx%xx%xx&at_preview_index=1_2&at_preview_listed_activities_only=truefor Experience B?at_preview_token=xxxxxxxx...

Re: Adobe Experience Cloud debugger with at.js 2.1 dosen't shows mbox request in summary section gokula - Adobe Target

Hi @mikewebguy Thanks for reply. Yes Debugging tool help to get the understanding on mbox but there few params campaign ID, recipe ID and others still not displayed. So can we bring this in debugger developr's team attentaion so that in next update we can have this as well

Likes given to

User

Count

Likes from

User

Count

Guidelines