SAP Marketing Cloud LinkedIn integration

SAP Marketing Cloud LinkedIn integration

You can now transfer a target group to LinkedIn Campaign Manager to create a Matched Audience in LinkedIn for your LinkedIn marketing advertising campaigns. Use the Matched Audiences to reach members on the LinkedIn professional network and drive sales or customer engagement.

You use the campaign execution framework to schedule the transfer of a target group to LinkedIn Campaign Manager. You can set a recurrence for the campaign to determine how often the target group is sent to LinkedIn to refresh the Matched Audience before the end date of the campaign.

You choose the ad account for whom the audience is created and the name of the audience that you’re creating in LinkedIn.

Once the target group reaches LinkedIn, the target group members are matched with the members of LinkedIn and those contacts who are in both systems are included in the Matched Audience.
Only those members who have opted-in to marketing permissions are included in the Matched Audience.

Please note that to keep the Matched Audience in LinkedIn synchronized with the opt-in and opt-out permissions of the target group members, the campaign must remain open.
Any target group members who opt out after the transfer to LinkedIn are removed from the Matched Audience on a daily basis. The Matched Audience is no longer refreshed when the campaign in SAP Marketing Cloud has reached the end date.

LinkedIn Campaign Manager

All set? You can then create a campaign in LinkedIn to target those customers specifically on the LinkedIn platform.

Choose ‘Next’ to setup your LinkedIn Campaign which consists of the following steps

• Objective selection
• Audience
• Ad format
• Placement
• Budget & Schedule
• Conversion Tracking

Choose the Matched Audience based on the target group you selected in SAP Marketing Cloud, select the ad format, placement and budget you want to spend on your ad.
Forecasted results are shown at the right to better understand the impact and costs of your LinkedIn ad campaign.

Finally, set-up you ad and review & launch your LinkedIn ad campaign.

Please not that the LinkedIn Audience Transfer action in campaigns is only used to transfer contacts, not accounts.
Also, the campaign in SAP Marketing Cloud isn’t connected to any campaigns in LinkedIn, and therefore we don’t read back any performance data from those campaigns. The campaign performance can only be analyzed in the LinkedIn Campaign Manager overview where several performance charts are available.

SAP Marketing Cloud – Show Additional Contact Origin ID in Contact Profile

How to show Additional Contact Origin ID’s in Contact Profile which is not visible in the Data Origin tab?

Since release 2102 the Additional Contact Origin ID is available by default on the Personal Data tab on the Contact Profile in the section ‘Business Partner Identifier’ in addition to ‘Inspect Contact’ and ‘Segmentation Models’ app in which the different Origins can already be checked.

SAP Marketing Cloud – Segmentation Attribute not visible in Segmentation Model

Symptom

A certain segmentation attribute is not available in the segmentation model, although the attribute is flagged as ‘visible as attribute’ and assigned to an attribute group.

Reproducing the Issue

1. In the segmentation configuration app, flag an attribute as ‘visible’ and assign the same to an attribute group available in the segmentation object
   
2. Create a segmentation model for the segmentation profile using the underlying segmentation object
3. Observe that the attributes is not available in the segmentation model
   

Cause

The attribute visibility might be overruled on segmentation profile level.

Resolution

Having the segmentation attribute flagged as ‘visible as attribute’ on segmentation object level is a prerequisite for having the attribute available at all. The attribute however must be flagged as ‘visible’ on segmentation profile level as well using the ‘attribute visibility’.

Make sure to have the attribute set to visible in the segmentation profile as well.

Then only the attribute is available in segmentation.

See Also

Please also refer to the online help:

• Segmentation Object – Attribute Settings – Display
• Segmentation Profile – Attribute Visibility

Another cause for a similar issue is documented in the following KBA:

• 2763176 – SAP Marketing – Segmentation Attribute not available in Segmentation Model

SAP Marketing Cloud – Permission Import failing due to duplicate Records

Symptom

A marketing permission import containing several permissions in the payload is failing with the following error:

“Multiple permissions with the same key at &1 found. Processing rejected.”

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

SAP Marketing Cloud Edition
SAP Marketing OnPremise starting with release 1709

Reproducing the Issue

1. Create a contact with with different source IDs but similar communication details like email, mobile or phone ID.
   
2. Import marketing permissions either via API API_MKT_CONTACT_SRV or via the Data File Load app. The API or CSV payload contains permissions records for the same contact.
3. Observe that the permissions import is failing with the following error in the import monitor.
    
4. On checking the payloads in detail, you observe that the permissions were imported for different IDs.
   

Cause

Marketing permission import requires two pairs of contact IDs – one pair of contact ID origin and ID for identifying the contact (CONTACT_ORIGIN and CONTACT_ID) and one pair of contact ID origin and ID for setting the marketing permission (PERMISSION_FACET_ID_ORIGIN and PERMISSION_FACET_ID).

The CONTACT_ORIGIN and CONTACT_ID pair is used for identifying the contact. After the contact is determined, the CONTACT_ORIGIN and CONTACT_ID information is discarded, as the permission processing happens on contact level but not on ID level – after the contact is determined, technically the processing happens via CONTACT_KEY and PERMISSION_FACET_ID_ORIGIN and PERMISSION_FACET_ID.

The CONTACT_ORIGIN and CONTACT_ID information is not persisted after the import.

Resolution

1. Avoid importing permission data with payloads for the same contact and permission IDs (so CONTACT_KEY and PERMISSION_FACET_ID_ORIGIN and PERMISSION_FACET_ID).
2. One suggestion to avoid that error is to separate the permission imports from different sources, so to implement the permissions from each source system individually.

See Also

Please also refer to the following KBAs for information about further permission import errors:

• 2941319 – SAP Marketing – Permission import failing due to wrong communication ID
• 2940770 – SAP Marketing – Permission import failing due to outdated timestamp

SAP Marketing Cloud – Segmentation Attributes from extension data source _SAP_CF_CE_CONTACT_IA_ERP_CUST

Symptom

In SAP Marketing Segmentation you create a segmentation model using segments. Each segment reflects a segmentation rule. The count in a child segment might not consider the segmentation rules from its parent segments in the segment tree as expected. When executing an email or file export campaign, the attributes in the campaign content are not necessarily created following the segmentation rules as expected.

Environment

SAP Marketing Cloud Edition

Reproducing the Issue

1. Log on to Fiori Launchpad in Hybris Marketing
2. Open the Segmentation Models App and create a new Segmentation Model
3. Use different filters to create a segment as following, with using filters on the interaction type (IA_TYPE) and interaction date (IA_DATE) – the example has different IA_DATE attributes visible in the interactions group:
   
4. Observe different counts for similar filter values for different IA_DATE filters
   
5. When using a target group created from that segmentation model in a email or file export campaign, the campaign content is not created as expected. You might observe that there are multiple values for a certain attribute – the campaign content might not be following the segmentation rules from the segment tree.

Cause

This might be related to the following design – the design is explained based on the following example build in the Cloud Edition using the segmentation object SAP_CONTACT_ENGAGEMENT_SIN:

The segment tree is built using filter attributes from different data sources:

• ‘Interaction Date’ IA_DATE from DS SAP_CE_CONTACT_IA_ERP_CUSTOMER
  
• ‘Interaction Date’ IA_DATE from DS _SAP_CF_CE_CONTACT_IA_ERP_CUST
  

When combining different filters with attributes from different data sources, the different data sources are joined via the key of the segmentation object, the SAP_CONTACT_KEY in that case:

When using attributes from different data sources, the join of those data sources may result in different data being returned. This is the very basic design of SAP Marketing Segmentation, which is assuming/requiring that attributes which have a dependency between each other are coming from the same data source, unless the dependency is fully qualified by the segmentation object keys. In other words, the attributes can reside in different data sources if the dependency is fully qualified by the segmentation object keys. So all attributes which have more dependencies than just the segmentation object key, must reside in the same data source.

The example above is built based on the following data:

Contact	IA_TYPE	IA_DATE
1	SALES_ORDER	15.05.2018
1	APPOINTMENT	16.05.2018
2	SALES_ORDER	16.05.2018
2	APPOINTMENT	15.05.2018
3	SALES_ORDER	16.05.2018
4	APPOINTMENT	15.05.2018

Filter: IA_TYPE = SALES_ORDER and IA_DATE = 15.05.2018

If IA_TYPE and IA_DATE are on the same data source, the selection works with the logic “give me all contacts which have any interaction of type SALES_ORDER with the date 15.05.2018”. The ‘and’ is applied on interaction level. The result is contact 1 only:

If IA_TYPE and IA_DATE are on two different data sources, the selection works with the logic “give me all contacts which have any interaction of type SALES_ORDER and any interaction with the date 15.05.2018”. The ‘and’ is applied on contact level only but not on interactions level. The result is contacts 1 and 2:

The same design is valid within segmentation but also when using any target group from the segmentation model for creating content or export. The setting ‘Content and Export –
Apply segmentation rules during content determination’ in the General Settings in the Target Group Configuration, also considers this design. Detailed information about the setting is available in the online help:

General Settings for Target Groups

Resolution

This design needs to be considered when setting up the Segmentation Configuration but also when building the segment tree.

When using custom fields in Segmentation, created from the ‘Customer Fields and Logic’ app, the custom attributes are available in a generated extension data source. When looking at the example above, the standard data source SAP_CE_CONTACT_IA_ERP_CUSTOMER has the extension data source _SAP_CF_CE_CONTACT_IA_ERP_CUST generated – all standard attributes are included in the standard data source, as well as in the extension data source. It is therefore strongly recommended to hide the attributes from the standard Datasource but display the attributes from the extension Datasource in the Segmentation Configuration once extension attributes are used.

The example above is taken from the Cloud Edition using the segmentation object SAP_CONTACT_ENGAGEMENT_SIN, the same design is valid for various different Segmentation Objects in the SAP Hybris Marketing Cloud.

The Segmentation Configuration app is available in the Cloud Edition.

SAP Marketing Cloud – ‘View in Browser’ Functionality in Email Marketing Campaigns

Symptom

Trying to access a View in Browser Link from an Email which was sent few months earlier will result in a below error

Environment

• SAP Marketing Cloud Edition

Reproducing the Issue

1. Create an Email Content with View in Browser functionality
2. Execute Campaigns with the above created Email Contents
3. Try to access the View in Browser link in the Email after few months , we will notice above error page.

Cause

• Campaign which triggered the Emails should have been Ended or Stopped
• Campaigns are not stopped , but the Emails that were sent are older than 180 days

Resolution

‘View in Browser’ functionality requires the Campaign Execution details to be able to show the contents in the Browser.

As per the Campaign design, these details are removed from the system in the following scenarios.

1. When the Campaigns are Stopped
2. If the EMAIL OUTBOUND Interactions are older than 180 days.

SAP Marketing Cloud – Unable to delete emails and email templates in Content Studio

Symptom

You want to delete old emails that are not used anymore

Environment

SAP Marketing Cloud – SAP Marketing Cloud

Reproducing the Issue

1. Go to Content Studio App
2. Click on show  “All Content” on the top right-hand
3. Search old emails or e-mail templates

Resolution

1. In general all released emails or e-mail templates cannot be deleted, However there is a work-around for current editor.

2. Released content that was not used in a campaign can be set back to “In Preparation” status by opening it in the editor and pressing “Edit”. After that it can be deleted in the editor or the worklist.

• The old e-mail\template can now be deleted while the mail status has changed back to the “in preparation” status.

3. It is not possible to delete released e-mail\templates in the new ‘Lite editor’, because the feature to go back into the status “in preparation” is not yet supported.

• The only available solution would be to set the undesirable e-mail to “Outdated” status, this simply means that the e-mail is obsolete.
• You can create a filter to filtered out (exclude filter) the outdated e-mail if you do not want to see them.

Note: Restricted Users may not have the authority to edit or delete e-mail templates.

SAP Marketing Cloud – Emails not sent due to Campaign Execution Whitelist and Blacklist

Symptom

Emails from Test Send or from Campaign Execution are not sent – sending the emails fail with either one of the following error messages:

• “1 outbound request(s) have not been sent due to whitelist entries.”
• “1 outbound request(s) have not been sent due to blacklist entries.”

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

• SAP Marketing Cloud Edition
• SAP Marketing OnPremise starting with release 1709

Reproducing the Issue

1. Test send an email from either the Content Studio or from the Sender Profiles app
2. Observe that the email is not sent, instead you get one of the following errors:

• “1 outbound request(s) have not been sent due to whitelist entries.“

• “1 outbound request(s) have not been sent due to blacklist entries.“

Cause

Campaign Execution Whitelist:

• SAP Marketing Q Tenants require individual emails or email domains to be whitelisted before they can be sent.
• With the whitelist, you explicitly allow the entered recipients to get messages.

Campaign Execution Blacklist:

• Blacklisted emails or email domains are not being sent from SAP Marketing.
• With the blacklist you explicitly block recipients from getting messages

Resolution

Use the Campaign Execution Whitelist app or the Campaign Execution Blacklist app to maintain emails or email domains according to the requirement.

1. The Campaign Execution Whitelist is required for Q Tenants only.
2. The whitelist is valid only, once some entries are maintained.
3. An empty whitelist is not considered, and all mails are sent.

SAP Marketing Cloud – Campaign scheduled times changed after the daylight saving time

Problem

Your campaigns are scheduled 1 hour later after the daylight saving time.

Reproducing the Issue

1. Create a Campaign before daylight saving.
2. Check the Campaign scheduled time after the daylight saving.
3. The Campaign is scheduled at a different time.

Cause

• Time Zone of Segmentation Profile used in the Campaign is set to a different Time Zone than the Time Zone considered with the daylight saving.
• If nothing is set for Time Zone, it will take the default Time Zone(UTC-0).
• Ex. Let’s say the Campaign is scheduled at 9AM EST, which is 2PM UTC. The Segmentation Profile is set to GMT time so in the database, the start time is 2PM UTC-0. After the daylight saving in EST time, the Campaign scheduled time at 9AM EST will change to 10AM because 10AM in EST will now equal to 2PM UTC-0.

Resolution

1. Access “Segmentation Configuration” App.

2. Go to Segmentation Profile and select the corresponding Profile.

3. Edit the Profile to set the correct “Time Zone”.

 

SAP Marketing Cloud – Multichannel Campaigns now available

Combine External Campaigns with Direct Campaigns

It is now possible to execute multiple marketing events/campaigns in one single marketing campaign. Eg. You can send email messages and push notifications in parallel to the same target group and alongside also send your (external) target group to another DMP (eg. Google or Facebook).

Business Benefits
▪ In a single campaign, model the elements that belong together without having to create separate campaigns per channel
▪ Intuitively take follow-up steps on other platforms by transferring contacts based on activities in SAP Marketing Cloud campaigns

Key Capabilities
▪ Support for true multichannel campaigns: Combine steps executed in the SAP Marketing Cloud solution, such as sending emails or mobile push notifications with steps executed on other platforms, such as displaying ads through Google Campaign Manager.
▪ Hand over audiences and create or assign external campaigns anywhere in the automation flow.

SAP Marketing Cloud – Contact Best Record Email Address not taken from most reliable Source

Symptom

When importing/retrieving data, the email address of the contact’s best record is not coming from the ID origin data that is defined with highest priority, but is replaced by another email address.

Please check the following steps:

1. Import contact origin data from at least 2 different sources to SAP Marketing
2. Observe that in some cases the email address for the contact’s best record is not taken from the ID origin data defined with the highest priority

   

Cause

Usually the best record creation follows the ID origin priorities, the best record is considering the data from the ID origin defined with the highest priority. In case 2 different ID origins are defined with the same priority, the latest import will be considered (technically identified via the latest ‘OriginDataLastChgUTCDateTime’). Communication data, such as email, mobile or phone IDs, however, consider marketing permissions as well. Any explicit opt-in given for a email, mobile or phone ID overrules the priority of the contact ID origin – an email ID with an explicit opt-in will be considered for the contact’s best record although it is coming from the origin data defined with a lower priority.

In addition the design might be influenced from BAdI CUAN_UPDATE_IC_ROOT ‘Update interaction contact (Best Record)’.

Resolution

To understand how the communication data was merged into the contact’s best record, check the Inspect Contact app as a first step. If the communication details are not coming from the origin data with the highest priority, also use the Contact Profile app to check the marketing permissions, using the ‘Permission Marketing’ tab.

In this case the opted-in email address will be considered for the contact’s best record.

Please refer to the online help to understand the Contact’s Best Records concept in SAP Marketing Cloud in the context of Data Stewardship.

SAP Marketing Cloud – Error accessing Campaign App on a Mobile Device (tablet or smartphone)

You click the the Marketing tile / app via a mobile device and you receive the error: “app could not be opened either due to an incorrect SAP FIORI launchpad configuration or a missing role assignment”.Failed to resolve navigation target “#Initial-manageCampaignFlow”. This is most likely caused by an incorrect SAP Fiori launchpad content configuration or by a missing role assignment.

The reason this error message appears is that the Campaign App on the SAP Marketing Cloud is not supported on Mobile Devices. This App should only be used on desktop or laptop devices.

SAP Marketing Cloud Integration Flows 1911 release

Following my previous post on SAP Marketing Cloud Integration Flows for previous release, please find below the up-to-date integration flows of 1911 release with SAP Cloud for Customer:

Integration	Description
Confirm Business Activity Replication to SAP Marketing	Business Activity Replication from SAP Marketing
Confirm Lead Replication to SAP Marketing	Lead Replication from SAP Marketing
Replicate Business Activity from SAP Marketing	Business Activity Replication from SAP Marketing
Replicate Business Activity to SAP Marketing	Business Activity Replication to SAP Marketing
Replicate Business Attribute Assignment to SAP Marketing	Business Attribute and Assignment Replication with SAP Marketing
Replicate Business Attribute Set to SAP Marketing	Business Attribute and Assignment Replication with SAP Marketing
Replicate Business Partner Relationship to SAP Marketing	Business Partner Replication to SAP Marketing
Replicate Business Partner to SAP Marketing	Business Partner Replication to SAP Marketing
Replicate Campaign from SAP Marketing	Campaign Replication from SAP Marketing
Replicate Lead with Business Partner Address Information from SAP Marketing	Lead Replication from SAP Marketing
Replicate Marketing Lead to SAP Marketing	Lead Replication to SAP Marketing
Replicate Marketing Permission to SAP Marketing	Marketing Permission Replication to SAP Marketing
Replicate Opportunity to SAP Marketing	Opportunity Replication to SAP Marketing
Replicate Service Ticket to SAP Marketing	Service Ticket Replication to SAP Marketing
Request Campaign Interactions from SAP Marketing	Request Campaign Interactions from SAP Marketing
Request Marketing Permissions and Subscriptions from SAP Marketing	Request Marketing Permissions and Subscriptions from SAP Marketing
Value Mapping for SAP Cloud for Customer and SAP Marketing Integration	Value Mapping for SAP Cloud for Customer and SAP Marketing Integration
Deprecated – Replicate Lead with Business Partner Address Information from SAP Marketing	Lead Replication from SAP Marketing

For more info, please check api.sap.com.

SAP Marketing Cloud – Import Monitor does no longer visualize Data for Imports

After the SAP Marketing Cloud tenant upgrade to Release 1911, the ‘Data’ bubble in the Import Monitor is no longer working – the payload for failed imports can no longer be displayed.

Reproducing the Issue

1. Open the Import Monitor and navigate to an import in status error.
2. Use the ‘Data’ bubble to visualize the payload for the failed import.
   
3. Observe that the payload is not displayed as expected. Instead the ‘Data’ bubble disappears.
   

Cause

SMC Release 1911 introduced new authorization control for displaying payloads of imported data. Authorizations are now controlled via business catalog ‘Marketing – Settings for Import Header Payload’ SAP_CEC_BC_MKT_IHP_PC.

Resolution

• Open the related business role of the affected user in the ‘Maintain Business User’ app
• Assign the business catalog ‘Marketing – Settings for Import Header Payload’ to the business role

• Enable display authorization in the business role restrictions settings as required either for ‘Error’ or ‘Success’ Imports or both

Export button and Import button are invisible in Contact(s) app for SAP Marketing Cloud release 1911

If you open the Contact(s) app and check the buttons in menu, you do not see the export and import button anymore since release 1911.

The reason for this is that new catalogs are shipped with 1911 to provide option to control Export button and Import button in Contact app.

Please add the delta catalogs for the affected users.

• SAP_CEC_BC_MKT_ICA_PC (Marketing – Import Contact and Accounts)
• SAP_CEC_BC_MKT_ECA_PC (Marketing – Export Contacts and Accounts)

Cheers!

SAP Marketing Cloud – Campaign not creating Leads or Activities in SAP Cloud for Customer (C4C)

You are using SAP Marketing Cloud integrated with Cloud for Customer. In SAP Marketing you execute a Campaign with ‘Trigger Call Qualification’ or ‘Create Appointment’ Action but not all Leads or Appointments are transferred to C4C.

For example:

1. Create a Campaign in SAP Marketing
2. Assign any Campaign Action integrated with C4C, such as ‘Trigger Call Qualification’, ‘Create Appointment’, ‘Create Task’, ‘Create Phone Call’
   
3. Execute the Campaign
4. Observe that Leads or Activities are missing in C4C

Why is this happening?
There are certain prerequisites for the Integration Scenarios from SAP Marketing Cloud to Cloud for Customer to work.
As a technical prerequisite the Communication Arrangement for Scenario SAP_COM_0017 – ‘Marketing – Presales/Sales Integration’ must be set up.

From a business process point there are the following prerequisites:

• Trigger Call Qualification

  

  The ‘Trigger Call Qualification’ action is supposed to create Leads in C4C for interaction contacts from type person.

  If the executed for an account an interaction from type OUTBOUND_FAILED in communication medium BUSINESS_DOCUMENT with interaction reason as WRONG_IC_TYPE_02 is created. The Campaign Performance shows the number of failed interactions in detail.
  

  The contacts in SAP Marketing need to fulfill the following prerequisites:

  • contact must not be ‘anonymous’ so the contact must have a name
  • PHONE or MOBILE ID must be available
  • marketing permissions for the PHONE or MOBILE ID must be available

    If the contact does not fulfill those prerequisites an interaction from type OUTBOUND_FAILED in communication medium BUSINESS_DOCUMENT is created. The interaction shows the interaction reason as PERMISSION_MISSING, PHONE_MISSING or NAME_MISSING. The Campaign Performance shows the number of failed interactions in detail.

    

• Activities (Appointment, Task, Phone Call)

  

  The different campaign actions, ‘Create Appointment’, ‘Create Task’ and ‘Create Phone Call’ are supposed to create different Activity Types in C4C. The contacts in SAP Marketing need to be created as C4C Business Partners as well, technically the contact must have an SAP_C4C_BUPA ID.

  Those campaign actions do not create Leads in C4C. If the contact is not existing in C4C an interaction from type OUTBOUND_FAILED in communication medium BUSINESS_DOCUMENT is created. The interaction shows the interaction reason as SAP_C4C_BUPA_MISSING. The Campaign Performance shows the number of failed interactions in detail.

  

• Leads

Campaign Actions triggering Leads in C4C require different contacts compared to Campaign Actions triggering Activities in C4C.

 

Resolution

To resolve the issue, define correct Target Groups for each C4C integration scenario in SAP Marketing, so that each of the target group members fulfill the required prerequisites described in the Cause section.

SAP Marketing Cloud – Email content not available in “Show valid only” list in campaign

You maintain the communication category in email content and want to select it during campaign creation process. Then you find this email content is not available in the list when choose “Show valid only” option.

For example:

1.  Create an email content with communication category.
2.  Create a campaign and navigate to select email part.
3.  Click the help pop-up and choose “Show Valid Only” option.
4.  The expected email is not available in the list.

Resolution

Please maintain the same communication category in the Campaign.

SAP Marketing Cloud – Segmentation: Date attributes displayed with wrong date format

You use the Segmentation in SAP Marketing to filter on any date attribute. The segment itself and the preview show the date in the wrong format – it is expected to display the date in format DD.MM.YYYY, instead the date is shown in format MM/DD/YYYY.

For example:

1. Access Segmentation in SAP Marketing
2. Create a segment on any date attribute, such as ‘Date of Birth’
3. Observe that both, the segment itself and the preview show the date in a wrong format

This problem is happening because the date format is taken from the date format defined in the user defaults.

Resolution

Change the date format for the affected business users in the Maintain Business Users app.

The regional settings offer different date formats:

SAP Marketing Cloud: Embedding YouTube Videos in the Content Studio does not work

As a marketer you want to embed or insert the YouTube Videos when creating your email content in the Content Studio in SAP Marketing Cloud. However, when you try to emded the iFrame with the YouTube video in the email editor, it is blocked by SAP

Reason for this is that most email clients will block these iframes too, so SAP decided to block this on the email editor a.k.a. Content Studio as well.

Email Client	Iframe displays?
AOL Webmail	No
Gmail	No
Windows Live Hotmail	No
MobileMe	No
Yahoo! Mail	No
AOL 9	No
Apple Mail 3 / 4	Yes
Entourage 2008	No
Lotus Notes 6 / 7	No
Lotus Notes 8	Yes
Outlook 2000	Yes
Outlook Express 6	Yes
Outlook XP / 2003 / 2007 / 2010	No
Thunderbird	Yes
Windows Mail	Yes
Blackberry	No
iPhone / iPad	Yes
Symbian S60	Yes
Windows Mobile 5	No
Windows Mobile 6	Yes
Android (default client)	Yes
Android (Gmail client)	No

Resolution

Use an image of the YouTube video you want to add to your email and link to the video on YouTube instead.

SAP Marketing Cloud – How to save personalization settings in Fiori apps in SAP Marketing Cloud

Symptom

You want to store your personalization settings for tables in Fiori apps. For example, Campaign List or Contacts app.

Reproducing the Issue

1. Go to for example Campaign List app
2. Unhide additional column, for example campaign id
3. Sort id descending
4. Leave app and/or session
5. Logon again and go to Campaign List app: Personalizations are not stored

Resolution

1. Select the desired settings under the Settings option
2. Or change the column widths
3. Notice that a star appears with the keyword Standard
4. Click standard variant and it will open a pop-up
5. Click Save As and provide a name for variant. Select Select as Default option to set this variant as default
6. Settings are now saved in the new variant

NOTE: Every time making a change via settings, a * will appear which will allow user to save again.