When creating a Email Send activity in Journey Builder, the Salesforce Data Extensions folder and Shared Salesforce Data Extensions folder will never be present.
This is functioning as designed.
You would need to create a Salesforce Send definition via the Interactions tab in Email Studio and then use the Salesforce Email Send tile in Automation Studio, ...
There is no OOTB functionality but once we did a similar check on the project and that is how we proceeded -
Get the value from the AddedBy field from the ListSubscriber Data View, which would give you the AccountUserID number of the user who added a particular subscriber.
AMPscript is not a recommended tool to use when it comes to the segmentation of the audience. It is better to prepare your contacts in the Data Extension in advance and once an email is sent to add an additional layer of simple calculations and of course personalization by AMPscript.
You can use SQL Query in the Automation Studio to prepare the Data ...
Your request is understandable and requires several things:
Firstly, it is was not specified whether your form is actually a SmartCapture form of the custom one. For your case, it would be easier to create a CloudPage with a form that would be tweaked based on your needs.
Your case presumes dynamic validation of the input data into the form. In other words, ...
You can do it via simple Automation with several steps inside:
Data Extract Activity (with enabled feature to extract Data Extension, if not then open a ticket with SF Support) - that will move the Data Extension to the Safehouse;
File Transfer Activity - that will place the file with records from the Data Extension on the SFTP (also requires SFTP access in ...
First of all, to send an email, you need to have correctly configured Data Extension with Email Address data type field and of course, be sendable with relationship to the SubsriberKey.
You do have sendable DE and the relationship as well but your related field called email is Text data type.
What you need to do:
Change the email field’s data type to Email ...
Because Email Studio does not provide this option. Only in Contact Builder, you can manually add/edit/clear records.
Important note for consideration to be able to find and then selectively edit or clear some records from Data Extension in Contact Builder, this Data Extension should have a Primary key.
Assuming you are using the new Web Studio that's based on content builder, then you don't want to use InsertData, instead you need to use InsertDE, then should fix the 500 error it is experiencing right now.
It is possible.
Shared Data Extensions are physically located in Parent BU (ENT or Enterprise context).
They differ from "normal" DEs in the Parent BU in that they are accessible from inside other BU contexts through SQL and AMPscript / SSJS.
So, one vector to approach this is to try an attempt an SQL SELECT operation from child BU:
Set up an ...
Your function AMPscript function - InsertData has 3 issues:
You did not set a variable for it;
At the very end you have double-quotes after the @age variable;
Also at the very end, after the @age variable you have a comma but there are no more additional attributes and values specified.
Thus, your function should look like this -
SET @insertData = ...
Sounds to me like you need an automation in each business unit (with staggered schedules) to update a shared data extension.
In an Enterprise 2.0 account, subscribers are shared across all business units. The platform only keeps track of unsubscribes per business unit. So the concept of business unit membership is convoluted, because it's technically "...
There are multiple ways how to do it and more or less always depends on your experience with MC and technical expertise.
For example, one of the easiest ways would be to create an Automation with either SQL or Filter Activity, which would prepare the data and also refresh it with new records.
Once this is configured, you would need to create a Multi-Step ...
Create a filter on the API entry event
Use the Update Contact block in the Journey to log in a separate data extension (for your exclusion purposes) who qualified for emails in this journey. Just remember that you need to work around the limitations of this block to dynamically log the values for each customer - I would recommend this ...
There are two ways to do this with a rolling date:
This is by far the easiest way to do it and in most use cases is likely the best option. I know most people show a heavy preference towards SQL, but unless you are looking at an extreme volume, utilizing a filter here is likely to be easier to maintain and more performant. It does limit ...
There is no specific guideline on how to proceed in your case and it highly dependant on how many Journeys, Automations or Triggered DEs you have and thus you would need to check.
The problem here is that each "usage" type of Data Extension would require you to prepare a separate approach to see the result, for example:
To get Data Extensions used ...
Your issue is you are doing an INNER JOIN, which requires the record to exist in BOTH tables (DEs) in order to be returned. The OPs code is basically saying return all records that match on both tables but are empty on the second one. Since it cannot exist but also not exist, it returns 0.
As you are looking for records that are both in and NOT in the _Click ...
Welcome to SFSE!
Please review _Click Data View documentation, where it is shown that the SubscriberID field is not nullable, thus you cannot have WHERE clause with cl.SubscriberID is null and INNER JOIN at the same time, which makes you have 0 records in the result.
You should either adjust conditions in the WHERE clause or select another type of JOIN, ...
You are pasting into var testDE = DataExtension.Init("..."); Data Extension's Name, however you need to paste there External Key. So you can either adjust the code to have External Key instead of Name there or make the External Key = Name of the Data Extension.
Read here more.