What is the difference between the Contact key and the Subscriber key in Salesforce Marketing Cloud?
I need to be clear on these so I can absolutely transfer this information. I have read the help material but I think I need it with an example as I still don't quite get it.
Contacts and Subscribers
A contact is a person you send messages to through any marketing
channel. A contact typically appears in the All Contacts section, but
a contact record can also appear in other locations.
A subscriber is a person who opted to receive communications or
belongs to a particular channel. A subscriber lives in the individual
studios. Subscribers can be imported or created manually and are
stored in data extensions.
Keep in mind that all subscribers are contacts, but not all contacts are subscribers. With email, a contact is somebody you sent emails to, so a subscriber in Email Studio will always be a contact. You can have contacts whom you’ve never sent to who don’t appear in All Contacts. For example, contact information imported into a sendable data extension but not included in a send doesn't appear in All Contacts. A subscriber is only added to All Contacts once something is sent to them. For instance, you might send the contact email and mobile messages, so the contact could be a mobile subscriber, and not an email subscriber.
Resources
Related
enter image description here
We have used DocuSign Rest API and at times we are seeing duplicate entries against one receiver in DocuSign account under "Sent Items". Though the receiver is receiving the email once only. See attached image for reference. What does the "waiting for others" status indicates and under which scenarios this status will be generated?
waiting for others means that one or more of the signing recipients and/or certified copy recipients has not yet completed their action on the envelope.
The multiple rows in the Sent list means that you have sent the envelope more than once, you'll need to check your code to see how that is happening. I suggest that you have your code make a log entry every time your code calls the DocuSign eSignature API (and for create envelope calls, record the envelope id.)
If you can't figure out how your app is sending multiple envelopes when you expect that only one is being sent, use the API Request Logger to see what is being sent to DocuSign from your app.
Re: only one email was sent even though there were two or more envelopes:
Using the DocuSign web app, examine the envelopes that are in flight to check their recipients. It could be that the email address is incorrect in some of the cases.
Check your email tool. The two email notifications for two different DocuSign envelopes will be very similar and are collapsed by some email agents.
I have a web application wherein our users create contracts and we have integrated with DocuSign through an embedded recipient experience.
My web application is fairly involved in gathering the appropriate signers, sending emails, requesting signatures, keeping up with signer statuses, etc., and so I believe that an embedded recipient experience makes the most sense for us.
However, our first client using the integration has already been using DocuSign for some time and their signers (CEOs, CFOs and the like) are accustomed to logging into DocuSign, seeing envelopes in their inbox and clicking on them to sign - which is only possible in an integration by adding them as remote recipients. Embedded recipients cannot be associated to a DocuSign user account.
I'd like to keep using embedded recipients, but my client desperately wants to see envelopes created from my application in their DocuSign user account inbox and sign them from there without first having to log into my application.
Is there any clever way to deliver such a request with an embedded recipient experience? Even an atypical workaround, like sharing documents between the embedded recipient and the user account or some other recipient type of which I'm not aware, etc.?
Unfortunately not. When creating an embedded signing session the recipient becomes what's referred to as a Captive Recipient. Captive Recipients follow a different set of rules in regards to email notifications and presence in an inbox.
For example, Captive Recipients don't receive email notifications by default -- but they can supply an email to be CC'ed onto the envelope.
Since the Captive Recipient also has a universal account number, the user is technically part of an account outside of yours or your recipients.
IE: Your recipient views his inbox linked to his userId on account XXXXXXXXX.
The Captive Recipient is part of account YYYYYYYYYY with its own unique userId, so there's nothing for it to match up to.
If your app relies on embedded signing to load DocuSign envelopes into something like an iFrame, you can still do that without using an embedded recipient, which would give you the ability to load them through your webApp as well as let your signer access them via his DocuSign inbox.
To retrieve the signing URL, you make a POST call to https://{endpoint}.docusign.net/restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient with the following call body:
{
"returnUrl": "http://localhost/returnUrl",
"authenticationMethod":"email",
"email": "{recipientEmail}",
"userName": "{recipientFullName}",
"recipientId":"{recipientId}"
}
The problem....
We have a Web Application that bring in articles from various sources such as (google, bing, yandex).
We wish to add another source. The source is email subscriptions from scientific journals of which there are thousands.
We want our userbase to be able to signup for email subscriptions and pull them into the Web Application. As the subscription process requires an email and a confirmation of email step, this is pretty user unfriendly if an admin has to go and check emails all the time. We have a proposed workflow and would be interested to implement something like the following.
Proposed workflow
User goes to a custom subscription management page in our web
application
User enters the name of the subscription.
User presses 'save' User receives a unique email address from the application (i.e. subscription1233167845#mydomain.com)
user then takes this email and uses it to sign up for the email subscription with the scientific journal
system receives email from scientific journal asking for confirmation
system automatically verifies email address
email alerts received for journal
From here there are 2 possibilities
1) the application parses all resources in email and extracts links
which are submitted to the applications custom crawler
2) information
is scraped directly from email and added to the web application list
of articles
can it be done? Do you have a better way?? Thoughts?
I have this test schema:
A client can have multiple addresses and multiple contacts
For example, a secretary (contact) will receive a product purchased by the company (client) she works for.
So, the delivery needs a contact, an address and also needs to be bounded to a client. What's the best way to a Delivery know where and whom to deliver its produtcs?
If I attach Delivery to Address and Contact, I'll have 2 Client id's.
We have a senario whereby which we are tracking a contact forms submission via Adwords Conversion tracking code and assigning that as a PPC conversion.
This is a lead generation website; therefore the issue coming to light is that they have good SEO and receive a large amount of contact form submissions organically.
We need to find out the success of contact form conversions via the PPC and can then account that to ROI; therefore we receive a Bc on the contact form submissions and would like to know if there is a way in which we could tag all PPC contact form submissions details i.e. a email address etc and then we can separate those from SEO form submissions and then get them to look at those PPC enquiries only and feedback on the success.
Does anyone know of a solution, or the best way to attack this?
Thanks
Are you using Google Analytics? It should be able to determine the source of your leads so you can break them out into leads by SEO and leads by PPC.
Or are you trying to figure out the exact traffic source of each individual lead you receive in an email. I've used a tool called http://convertable.com which does exactly this since Google Analytics doesn't really track beyond the initial contact form submission.
Did you hear that AdWords launched a conversion import feature and API late last year? https://support.google.com/adwords/answer/2998031?hl=en
The case they talk about a lot is lead conversions. Here's how it works. Put simply, you capture the click ID from every ad click. If one of those people goes on to submit a lead, you store the click ID (called a GCLID) along with the lead's information.
Then, if the lead goes of to become qualified or even becomes a customer, you send the GCLID back to AdWords along with the date/time it converted, and AdWords records it as an actual conversion. They you can get reporting, or use their bid automation, to optimize for these.
Does that help?
Jon
We have a senario whereby which we are tracking a contact forms
submission via Adwords Conversion tracking code and assigning that as
a PPC conversion.
Why don't you just track the contact forms submissions as a analytics goal? if you want to add a value to them you can just give a fixed amount in analytics.
This is a lead generation website; therefore the issue coming to light
is that they have good SEO and receive a large amount of contact form
submissions organically.
We need to find out the success of contact form conversions via the PPC and can then account that to ROI;
You can look at Source/Medium in the Acquisition section, or in the Conversions section of analytics or create a custom report with this information.
therefore we receive a Bc on the contact form submissions and would like to know if there is a way in which we could tag all PPC contact form submissions details i.e. a email address etc and then we can separate those from SEO form submissions and then get them to look at those PPC enquiries only and feedback on the success.
you can associate email accounts to source/medium by tracking utm codes in the backend so that every time there is a submission you would have saved the utm_source and utm_medium parameters from the URL submission request (https://support.google.com/analytics/answer/1033867?hl=en).
Another way of doing this is using a fremium tool like KISS metrics - https://www.kissmetrics.com/ or mixpanel - https://mixpanel.com