SAP Marketing Cloud: Notify the same email address for each new lead

[former_member558862]

We are creating account and project leads via SAP Marketing Cloud "Create lead" campaigns and by using the manual push after leads got qualified. Now we were thinking if it is somehow possible to send some notification to one specfic email address each time a new lead was created. The email should contain information about the lead (at least the ID) so that the processors of the leads in C4C are aware of the new lead.

I was thinking about some trigger-based campaign based on the interaction segmentation profile, however, the email action of course would always only send to the contact of the interaction. I do not think that this can be adjusted.

Do you have any idea whether this can be achieved with the standard functionalities (in combination with some custom logic)? Of course, there is always some chance of doing a custom implementation on CPI, however, I would like to check if it can be achieved in a more simple way...

Thanks for your ideas!

[cc4f00ba-6b54-403d-bf1c-3]

Hello Christian,

I might have something useful.

We can create a Workflow Rule in C4C where, for example, the Sales Responsible Employee will receive an e-mail when the creation date field changes from 'empty' to the date of its creation.

1)

2)

Kindly check if this idea helped you. Hope it does.

Best regards,

Gabriel

[former_member558862]

isabelle.thore cc4f00ba-6b54-403d-bf1c-3233ad7ff438,

thanks for your ideas so far. Maybe it would also be an idea to send an email for each submitted form instead of just when a lead was created in C4C. I will think about whether this way there is also some way.

Best
Christian

[cc4f00ba-6b54-403d-bf1c-3]

Hi Christian,

Let me know your further toughts, when you have them, for curiosity purposes.

Thank you,

Gabriel

[former_member558862 · Accepted solution]

I was able to implement the requirement. Thanks to isabelle.thore for providing the final hint. Please find a summary below.

1) Create a new contact that should receive the notification emails

2) Create a custom interaction type (e.g. "Sales Notification") with communication medium "Web" via "Manage Your Solution" app

3) Enable the custom interaction type as campaign trigger via "Manage Your Solution" app

3) Add the interaction element (hidden & pre-selected) to your form

4) Implement BadI "Revise Interaction Data Before Import"

IF interaction_data-mkt_area_id = 'MHP' AND interaction_data-ia_type = 'Y_SALES_NOTIFICATION'.

* Get new contact’s name in order to store it to the interaction
	DATA: lv_name type c length 80.

	SELECT SINGLE FullName FROM I_Mkt_Contact
	WHERE InteractionContact EQ @interaction_data-contact_key
	INTO @lv_name.

	IF lv_name IS NOT INITIAL.
		interaction_data-content_title = lv_name.
	ENDIF.

* Create the interaction for the market contact address instead for the new lead

* Contact key is a different one on test and production system, therefore read it based on the facet (same in both systems)
* Launch URL of interaction probably not always containing the system ID
    SELECT SINGLE InteractionContact
	INTO @data(lv_contact_key)
	FROM I_MKT_ContactFacet
	WHERE InteractionContactOrigin EQ 'YOUR_SALES_CONTACT_ORIGIN'
	AND InteractionContactId EQ 'YOUR_SALES_CONTACT_ID'.

* Set general contact only if contact was found based on facet
    IF lv_contact_key IS NOT INITIAL.
        interaction_data-id_origin = 'YOUR_SALES_CONTACT_ORIGIN'.
        interaction_data-id = 'YOUR_SALES_CONTACT_ID'.
        interaction_data-contact_key = lv_contact_key.
    ELSE.
* Otherwise do not create the interaction (something must be wrong)
        exclude_from_import = 'X'.
    ENDIF. 

ENDIF.

I set the name of the contact who submitted the form as content title. Of course, you can also use different information.

Furthermore, the sales contact in the test system has of course a different key than the one on production. I did not feel comfortable to rely on the launch URL of the interaction since I am not sure if it does always contain the system ID when hosted somewhere else. Therefore, I made sure to use the same identifying origin/ID combination on both systems to read the interaction contact key.

The interactions are correctly written after the BadI was implemented (don't be confused by the strange test contact names).

5) Create a trigger-based campaign with the custom interaction type as campaign trigger. Use the email action to send out the notification. For the campaign and the content make sure to use the interaction-based profile. The content can then for example contain the name (content title).

To make sure only the specific sales contact receives notifications, you can of course also add a live target group in addition.

[isathore]

HI Christian,

Sorry for the delay. What we could suggest to look at is:

1. Create a contact that represents the internal stakeholder
2. Use the interaction Revise BAdI to create an interaction (custom type Lead Created for example) for this internal stakeholder
3. Have trigger-base campaign picking this up and sending a email to this internal stakeholder

Would that work for your business case?

Best Regards

Isabelle

[former_member558862]

Hi isabelle.thore. I already tried it with that BadI but got stuck with the approach to create an additional interaction. But now I think I know what you mean and definitly makes sense. In the form I will add the custom interaction which is always checked and hidden. For those interactions I will always replace the contact using the BadI and create some campaign to send out the email. I can probably also use the BadI to define some logic to fill the custom interactions content subject with information about the form submission (e.g. name of the new lead) that can then be used to personalize an interaction-based email content.

Due to 2302 upgrade preps I am currently blocked in the configuration but will comment when I got some result 🙂

[andreasfranz]

Hi,

I guess the additional IC subnode it not the right entity to use, for several reasons:

-Additional IC are not used for trigger based campaigns

-additional ICs are only used in the segmentation content for "Contact Relationships"

-IAs with Add IC are only shown on the contact factsheet in case the usage of Projections/Contact Relationships is turned on.

I would try to duplicate the interaction within the BadI, change the contact and use it as a trigger.

Best regards

Andreas

[former_member558862]

I was trying to work with custom logic "Revise Interaction Data Before Import" and the additional interaction contact object:

The additional contact linked is the one with the general email address that should be notified. The contact is correctly linked to the interaction as "Additional Interaction Contact":

However, unfortunatelly this does not mean that the interaction is duplicated to that additional contact. So it can not be used as trigger for the additional contact...

[isathore]

Hi Christian,

I might have an idea. I am currently validating.

Best Regards

Isabelle

[former_member558862]

Hi isabelle.thore,

thanks for taking the time. Looking forward to your idea...

Best
Christian