A retail company would like to send a promotional offer to their loyalty customers which is redeemable by a phone call to their customer call center The segmented population for the send is 23,500 and the customer center is equipped to redeem 5,000 offers each day.
How would a business practitioner ensure that the offers are controlled in a sequential send?
To manage the flow of promotional offers and ensure the call center can handle the redemption volume effectively, the business practitioner would need to implement a controlled delivery process. By creating an incremental send for 5,000 offers, the practitioner can distribute the promotional offers in manageable batches. The application of the Filtering Typology rule serves to halt the send process once the daily limit of 5,000 offers is reached, ensuring that no more than 5,000 customers are contacted per day. This approach prevents overwhelming the call center and helps maintain an organized redemption process. The typology rule will filter out any additional sends after the daily quota has been met, resuming only the next day with the next batch of 5,000 until the entire segment of 23,500 is covered. Reference: The response is based on the understanding of typology rules and send management within Adobe Campaign Classic or similar campaign management systems, ensuring the delivery process aligns with the operational capacity of the call center.
A customer needs to create a web form, which collects and stores anonymous users' email, First name, Last name, and color preferences, to an Adobe Campaign Classic database.
What kind of structure should be used to save data coming from the web form?
You can use a custom data schema linked to Recipient when you want to store data in a separate table and link it to the recipient table1.
When collecting data from a web form that includes both identifiable information (such as first and last name) and preferences (such as color preferences), the best practice is to store this information in a custom data schema that is linked to the recipient. This linkage allows the stored data to be associated with a specific recipient, which can be anonymized initially and then identified later if necessary. By using a custom data schema, you can extend the recipient schema to include additional fields without modifying the out-of-the-box recipient schema, ensuring that the database remains organized and scalable for future needs. Reference: This answer is based on best practices for data management in Adobe Campaign Classic and similar marketing automation platforms, which often involve creating custom schemas for additional data collection while maintaining a link to the central recipient or customer schema for proper data association.
A customer wants to trigger an email on a specified frequency based on the customer journey.
Given that the customer wants the delivery statistics consolidated, what kind of email delivery should the business practitioner configure in this scenario?
In scenarios where a customer wishes to trigger emails based on the customer journey and wants consolidated delivery statistics, a recurring delivery is appropriate. This type of delivery repeats at specified intervals, which can align with the frequency dictated by the customer journey stages. By pulling content from the delivery template, the practitioner ensures consistency in the email content across different sends while benefiting from the cumulative statistics that a recurring delivery provides, allowing for a consolidated view of delivery performance over time. Reference: Recurring deliveries are a feature within Adobe Campaign Classic that allows for the repeated sending of a delivery on a set schedule, which is useful for consistent communications and consolidated reporting.
A business practitioner needs to identify the total number of complaints for a given delivery by domain.
What out-of-the-box report would provide this information?
To identify the total number of complaints for a given delivery by domain, the 'Non-deliverables and bounces' report would be appropriate. This report typically includes data on email delivery issues, which encompass bounces, spam complaints, and other non-delivery related events categorized by domain. Complaints are a form of non-deliverable where the recipient's email server has accepted the email but classified it as spam or junk, often feeding back to the sending server as a complaint. Reference: This functionality is part of Adobe Campaign Classic's reporting capabilities, providing insight into the deliverability issues including complaints by domain.
An Adobe business practitioner needs to export a report on user activities with various reporting tools within Adobe Campaign. The business practitioner would like to know how many times each report has been generated and how many unique users used it.
What is the best practice to accomplish this task?
Adobe Campaign provides several reporting tools that can help analyze and represent data for different purposes. Some of these tools are:
Audit features: These features allow you to track and monitor user activities on various objects and folders in Adobe Campaign, such as deliveries, workflows, reports, etc. You can access them under Administration > Audit folder.
logins.log file: This file records all the login attempts to Adobe Campaign server, including successful and failed logins. You can access it in the nlserver syslogd module.
Delivery summary report: This report shows a summary of the delivery settings and statistics, such as target population, subject line, sender name, etc. You can access it in Adobe Creative Cloud.
This would allow you to export a report on user activities with various reporting tools within Adobe Campaign. You would be able to see how many times each report has been generated and how many unique users used it.
Jennifer Hall
16 days agoKaren Campbell
23 days agoFrank Nguyen
2 months agoDonna Brown
2 months agoAngela Moore
2 months agoRonald Lopez
3 months agoCharles Lee
2 months agoDavid Rivera
2 months agoSarah King
2 months agoDaniel Clark
2 months agoRyan Thomas
3 months agoKayleigh
4 months agoJaleesa
4 months agoAja
4 months agoMatthew
4 months agoJosphine
5 months agoYvonne
5 months agoElenora
5 months agoHillary
5 months agoRashad
6 months agoHerschel
6 months agoLemuel
6 months agoWalker
6 months agoVallie
7 months agoCherry
7 months agoHelene
7 months agoHailey
7 months agoNorah
8 months agoBrande
8 months agoAntonio
8 months agoLavonda
8 months agoWenona
9 months agoOmega
9 months agoTheola
9 months agoJamal
9 months agoGlory
10 months agoGlory
10 months agoCarmen
10 months agoClay
10 months agoSarina
1 year agoPhung
1 year agoMerrilee
1 year agoPearly
1 year agoJess
1 year agoMartina
1 year agoHoa
2 years agoLorrie
2 years agoSherill
2 years agoEarleen
2 years agoTamera
2 years agoDenny
2 years agoLindsey
2 years agoLemuel
2 years agoKati
2 years agoLyda
2 years agoCeola
2 years agoCrista
2 years agoRessie
2 years agoAlton
2 years agoLuz
2 years agoKiley
2 years agoJanna
2 years agoDottie
2 years agoZachary
2 years agoHaydee
2 years agoCarri
2 years agoKaycee
2 years agoEura
2 years agoAllene
2 years ago