email implementation

Hi @michael_soprano 

I know your post is a couple of months old, so you may have already been able to fix it, however. I'm posting my comments so it hopefully can help someone else with similar questions in the future.

---

• emailHeroImage123_320x200 - it can be whatever name? 
• mboxDefault - here I need to put url of hosted photo in URL encoded format?

---

emailHeroImage123_320x200 Yes, it can be whatever name. It is the name that will appear in the Target UI as your 'location'. So best practice is to give it a name, so it is easy to understand where in the email you're replacing content/what location you're setting up an activity for. Example: email_header.

mboxDefault Correct. It is required that it is an image and it will be shown as default content. Meaning if Target is not serving anything, then this will be the image that will be shown to your email readers.

3. Then I am supposed to create redirect offer for every alternative image? 

---

Yes. This dosn't have to be a separate step, but can be done as part of step 4 (creating the activity). When using an adbox you need to create the activity using the form based composer. Here's the steps for creating an redirect offer using the form based composer: https://experienceleague.adobe.com/en/docs/target/using/experiences/offers/offer-redirect#create-a-redirect-offer-using-the-form-based-experience-composer

Note that the 'location'-dropdown (above the content section that is highlighted in the screendump) this is where you'll have to select the name you've used. In your example above it is: emailHeroImage123_320x200

 

5. But how I implement this in my HTML code of an email? 

---

Identify the html for the image you wish to be replacing/testing in your email. Without Target implemented - and in it most simplest form - it will typically look something like this:

You need to replace the src value with adBox URL, so it eventually will look something like this:

To make it easier to read, I've listed each parameter in it's own line. Usually they would just be in one single line.

There's a few more parameters that I've added, besides the ones you covered yourself in your question:

• mboxXDomain:
  Set to disable tells Target to not try and set cookie
• mboxSession & mboxPC:
  Two values required by Target to merge this user’s profile with the existing profile for your site. 123456 is the unique identifier generated per email. Dynamically insert this value into every adbox and redirector URL. This number must be unique for each email sent to each person. If a weekly email is sent to 1,000 people, 1,000 unique IDs need to be generated.
  
  The unique identifier per email needs to be assigned to the mboxSession and mboxPC in each adbox and redirector URL. The recommended format for this identifier is timestamp-NNNNN where NNNNN is a random 5-digit number, but any alphanumeric format will work. Some mass e-mail services and any programming language are capable of generating this unique identifier.

I hope this helps you or anyone who have similar questions.