Any integration that is authenticated using OAuth will be unaffected by a reset of the security token.
Any integration that is authenticated via a username and password stored by the remote system may be affected, depending on your specific security configuration and whether or not the remote system is located inside your trusted networks.
While you can ...
Reference this doc 'Create Synchronized Data Sources in Contact Builder'
Filter the synchronized records you choose to import using the Records Collection buttons.
To import all records, select All records.
To import only records with an email address, select All records with
an email address.
To import only records created after a specified date, select ...
The field on the left is a regular text field, so you can do the following:
copy the moustached variable
select the next value from the attribute list and paste the copied value alongside it in the configuration field on the left
separate the moustached codes with something so they're more readable like / or even hard-code some comments
repeat for any other ...
This is immutable, expected behavior done by the MC Connect Managed Package. And before you do anything else: Email is a terrible, terrible Subscriberkey, please do NOT put any efforts into making it yours.
People share email addresses.
People change email addresses. (google "natural" vs "surrogate" keys). Email address is Personally ...
I experienced this same error after configuring MC Connect. I went over the configuration to make sure all steps were followed correctly, and noticed that SFDC needs a little bit of time to finish all the automated processess.
After 5-10 minutes I went to the Marketing Cloud tab in SFDC, clicked on "Connect to Marketing Cloud" (it did not show me ...
Documentation about MC Connect and authentication between clouds:
Quote from above documentation:
"Connected App Authentication is a secure authentication mechanism used by Marketing Cloud Connect. It removes the need to manage any Sales or Service Cloud user passwords in ...
that sounds like a bit of a bold undertaking and I would discourage the approach you lay out.
Here is my reasoning:
Are you aware of the potential performance drops when using the sales cloud AMPscript functions? Be sure to test "updateSingleSalesforceObject" at scale if you want to use this in larger sendouts to ensure this doesn't slow your ...
It could be your dates in the where clause.
Try to cast the dates and use datediff in your sql where clause so it's not comparing strings, apply date diff for both comparisons. For example.
DATEDIFF(day, CAST (Account_Fund_Date__C AS DATE), CAST("2020-09-30" AS DATE)) <=0
MobilePush SDK needs to set the correct ContactKey in order to match the Device with the Contact in Contact Builder.
Thus, in the context of this question, the mobile App has to know the Salesforce ID of the Contact prior to setting the ContactKey during the device registration.
In my use case, the mobile App performs an API call to Salesforce Core APIs to ...
Turns out that the Salesforce documentation is outdated! I had to use MOBILE_NUMBER and not _MobileNumber in the SMS message. Now it works!
For those interested in the solution:
Whenever a subscriber texts STOP, the response message contains code to update ConsentToTexts__c to FALSE and PreferredCommunicationMethod__c to “Email”, for all Contact records ...
Easiest way to achieve this is based on a shared email address value, so when an unsubscribe takes place for a subscriber, you're able to also unsubscribe any other subscriber keys that share the same email address.
An automation can achieve this in four steps:
SQL query returning Subscriber Keys where the associated email address has at least one ...
Went back and redid the entire connector process, there was a setting that was not enabled and it fixed the error issues. Make sure you're meticulous about it on both sides (Sales & MC) and it should work after.
After more research and speaking to others on this, it appears that email tracking data is all that is sent to Salesforce via the connector. One solution is to do the work manually, creating a custom object (which the connector does for you in the case of email sends) and populating this with the Push engagement information.