Expand my Community achievements bar.

SOLVED

Understanding Outbound Records for Recipients

Avatar

Level 2
Level 2

Hi Experts,

 

I have a query related to filtering dimensions and outbound records in Adobe Campaign Classic.

 

Case 1:

 

Target Dimension: Recipient

 

Filtering Dimension: Recipient

 

Condition: Delivery logs exist, where the delivery name is included in 'abc', 'xyz'.

 

 

Case 2:

 

Target Dimension: Recipient

 

Filtering Dimension: Delivery logs (Broadlog Rcp)

 

Condition: Delivery name is included in 'abc', 'xyz'.

 

 

Scenario:

If a customer is present in both deliveries (abc and xyz), how many outbound records will be generated in each case? Will it be only one record or two, and why?

 

Looking forward to your insights to understand how the filtering and target dimensions impact the result.

@ParthaSarathy @Marcel_Szimonisz @_Manoj_Kumar_ 

 

Thanks in advance!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@KD1 ,

It depends on the field you select in 'Add data'.

In keeping Targeting dimension as recipient and filtering dimension as BroadLogRcp, there are 2 scenarios.

In scenario-A, if you select only 'address' and [recipient/@id] and any other fields of the recipient which has same value in the Query > Add data, the output will be 1.

In scenario-B, if you select broadLogRcp's Primary key or Event date or delivery internal name, the output will be 2. This is an expected behavior. But why in this Scenario-A the output is 1 because by default 'Remove duplicate rows' be enabled in Advanced parameters. If you uncheck it, for the Scenario-A also the output will be 2.

ParthaSarathy_0-1734938536831.png

In your case after Query, you can have deduplication activity and dedup based on primary key of recipient or by deduplication on email/mobile number.

View solution in original post

10 Replies

Avatar

Community Advisor

Hi @KD1 ,

In both the configurations the output will be one record (as the Targeting dimension is recipient).

Whereas if the targeting dimension is broadLogRcp, then the output will be 2 records as per your scenario 

Filtering dimensions 

Avatar

Level 2
Level 2

Thank you for the quick reply!

I tried running both the queries and observed the following:

Case 1: I am getting 1 record.

Case 2: I am getting 2 records.


I have attached a snapshot for reference. Could you please review and advise why there is a difference in the output between the two cases?

Looking forward to your guidance!

Avatar

Community Advisor

@KD1 ,

Share the configurations of Query-2. This might be if you had configured group-by in query's Add data with recipient I'd and any other fields from broadLog, say for example recipient I'd with broadLogRcp I'd or with event date or with delivery I'd etc

Avatar

Level 2
Level 2

Hi,

Please find attached the configuration for Case 2, where:

Target Dimension: Recipient

Filtering Dimension: Delivery Logs (Broadlog Rcp).

IMG_20241223_094452.jpgIMG_20241223_094342.jpgIMG_20241223_094222.jpgIMG_20241223_092500.jpgIMG_20241223_092301.jpgIMG_20241223_092043.jpgIMG_20241223_094802.jpg
Could you please review and advise on this configuration?

Thank you!

Avatar

Level 2
Level 2

Hi @ParthaSarathy 

I have cross-checked again, and my configuration is as follows:

Target Dimension: Recipient

Filtering Dimension: Delivery Logs.IMG_20241223_092500.jpg

Kindly refer to the attached snapshot for your reference.

 

Avatar

Correct answer by
Community Advisor

@KD1 ,

It depends on the field you select in 'Add data'.

In keeping Targeting dimension as recipient and filtering dimension as BroadLogRcp, there are 2 scenarios.

In scenario-A, if you select only 'address' and [recipient/@id] and any other fields of the recipient which has same value in the Query > Add data, the output will be 1.

In scenario-B, if you select broadLogRcp's Primary key or Event date or delivery internal name, the output will be 2. This is an expected behavior. But why in this Scenario-A the output is 1 because by default 'Remove duplicate rows' be enabled in Advanced parameters. If you uncheck it, for the Scenario-A also the output will be 2.

ParthaSarathy_0-1734938536831.png

In your case after Query, you can have deduplication activity and dedup based on primary key of recipient or by deduplication on email/mobile number.

Avatar

Level 2
Level 2

@ParthaSarathy  Thank you for clearing my doubt! I now understand the difference

I need your help with a few additional questions:

 

1. In Case 2, where the Target Dimension is Recipient and the Filtering Dimension is Delivery Logs, is this the best approach for querying the database?

 

2. What should be the Target Dimension and Filtering Dimension to check for customers who have opened or clicked on a delivery?

 

3. What should be the Target Dimension and Filtering Dimension to check for customers who received a specific communication, such as "xyz"?

 

Looking forward to your guidance!

Avatar

Community Advisor

@KD1 ,

1. In Case 2, where the Target Dimension is Recipient and the Filtering Dimension is Delivery Logs, is this the best approach for querying the database?
 - Yes, This is the best approach. You can refer this document explaining why this is best.

2. What should be the Target Dimension and Filtering Dimension to check for customers who have opened or clicked on a delivery?
-Keep both targeting and filtering dimensions as Recipient, In query editor give ,
TrackingLog exist such as
Delivery code equal to abc

3. What should be the Target Dimension and Filtering Dimension to check for customers who received a specific communication, such as "xyz"?
-Keep both targeting dimension as recipient and filtering dimensions as broadLogRcp, In query editor give ,
Delivery code equal to xyz
AND
status equal to sent