Hi all,
i'd like to know if there is any way to change the datastreamId where the data are sent during the elaboration of some conditions.
Is there a way to detect the datastream and then change it, maybe inside a rule?
Thanks in advance!
Solved! Go to Solution.
Views
Replies
Total Likes
I see that you are asking about "dataStreamId" and not "dataSetId".
The dataStream is selected (per Launch environment) in the AEP Web SDK main configuration. This setting is tied to the "instance" - most people only have one instance and take the default instance name of "alloy".
What you're asking to do seems possible, but also pretty complicated. Here's how I see it as being possible.
It is possible to have multiple AEP Web SDK instances (each with different data stream settings).
Let's say that you create two instances and name them "alloy A" and "alloy B".
"alloy A" sends data to the edge using dataStream A (which in turn populates AA Report Suite A).
"alloy B" sends data to the edge using dataStream B (which in turn populates AA Report Suite B).
You can create a rule with the appropriate conditions that does an XDM Send using the "alloy A" instance. You can then create an other rule with (hopefully mutually exclusive) conditions that does an XDM Send using "alloy B". I think that I'd include some indication of the instance in the rule name so that you can keep things straight in the UI.
IDK if this is an appropriate solution for you, but it's a solution nonetheless. ![]()
Hello @nico9
You can select the data set where you want to ingest the data in the launch rule.
Here is the screenshot where you can add the data set id.
Views
Replies
Total Likes
Thanks for the answer!
unfortunately it seems to be a little more complicated as i want to change not only the dataset but actually also the reportsuite for analytics. so i'd like to send certain data to a datastream with different configurations.
Views
Replies
Total Likes
The "Dataset ID" field that @Manoj_Kumar_ mentioned can accept a data element. So you can have a data element that returns the dataset ID that you need, and use that data element in this Web SDK action.
Views
Replies
Total Likes
I see that you are asking about "dataStreamId" and not "dataSetId".
The dataStream is selected (per Launch environment) in the AEP Web SDK main configuration. This setting is tied to the "instance" - most people only have one instance and take the default instance name of "alloy".
What you're asking to do seems possible, but also pretty complicated. Here's how I see it as being possible.
It is possible to have multiple AEP Web SDK instances (each with different data stream settings).
Let's say that you create two instances and name them "alloy A" and "alloy B".
"alloy A" sends data to the edge using dataStream A (which in turn populates AA Report Suite A).
"alloy B" sends data to the edge using dataStream B (which in turn populates AA Report Suite B).
You can create a rule with the appropriate conditions that does an XDM Send using the "alloy A" instance. You can then create an other rule with (hopefully mutually exclusive) conditions that does an XDM Send using "alloy B". I think that I'd include some indication of the instance in the rule name so that you can keep things straight in the UI.
IDK if this is an appropriate solution for you, but it's a solution nonetheless. ![]()
Thank you! It is a good and linear solution!
Views
Replies
Total Likes