Free AD0-E307 Practice Test Questions and Answers (2026)

The 'Enable but do not execute' execution mode is a debugging feature in Adobe Campaign Classic workflows. When this mode is set on an activity, the workflow engine processes all preceding activities and enables the inbound transition to the selected activity, but it pauses execution before running the activity itself. This effectively creates a breakpoint, allowing a developer or operator to right-click the inbound transition and select 'Display the target...' to inspect the data payload (the records) that has reached that point in the workflow. This is crucial for verifying intermediate results, such as the output of a query or data reconciliation, before proceeding.

A. to skip the activity and continue workflow execution This is incorrect. The workflow does not skip the activity and continue; it explicitly stops at this activity, and subsequent activities are not executed.
B. to dynamically reconfigure the activity This is incorrect. This mode is for pausing and inspecting data. Reconfiguration of a running workflow is not its intended purpose.
C. to step into the activity and execute stepwise This is incorrect. The activity is explicitly not executed in this mode. Therefore, there is no execution to "step into." The pause occurs before the activity begins processing.

1. Adobe Experience League - Campaign Classic Documentation. In the section describing workflow activity properties, the 'Enable but do not execute' mode is defined. It states: "the activity is not executed, but the input transition is enabled. This option is used for debugging: it lets you check the intermediate results of a workflow, for example by displaying the target of a query. The workflow stops at this activity, and the subsequent activities are not executed."

Source: Adobe Campaign Classic v7 Documentation, "Workflow properties", Section: "Execution" tab (under Activity properties).

URL: https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/monitoring-workflows/workflow-properties.html?lang=en

The "auto detect format" feature in Adobe Campaign Classic's Data Loading activity is an automated assistant, not a definitive solution. While it attempts to determine the file structure, delimiters, and data types, it is not guaranteed to be 100% accurate. It is especially prone to misinterpreting ambiguous data types like dates, which can be represented in many different formats (e.g., YYYY/MM/DD, MM-DD-YY, DD.MM.YYYY). Therefore, the mandatory next step is to manually review and verify the detected format, paying special attention to ensure date columns are assigned the correct format mask to prevent data corruption or import failures.

A. Load a file from your local machine to test the format: This step precedes clicking "auto detect format." A sample file must already be loaded or selected for the auto-detection feature to analyze.
C. You can move forward, auto detect formats the file properly: This is a dangerous assumption. Relying solely on auto-detection without verification is poor practice and can lead to significant data integrity issues.
D. You should create a new data loading process and leave the original intact for future use: This is a workflow management decision, not the immediate technical step required to correctly configure the current file format being processed.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Data loading (file)": In the section describing the "File format" tab, the documentation details the manual configuration options for file structure, including column data types. It states, "For columns containing dates, you can specify the input format." This implies that even after auto-detection, user verification and potential manual adjustment are required steps to ensure formats, particularly for dates, are correct. (See the "Defining the file structure" subsection within the "File format" activity properties).

2. Adobe Experience League - Campaign Classic v7 Documentation, "Get started with workflows - Use case: load a file": This tutorial guides users through the data loading process. In Step 2: "Configure the file loading activity," it emphasizes the need to "Define the file format" and check the column properties. The interface shown allows for explicit setting of data types and formats, reinforcing that this is a critical user-controlled step, not one to be left entirely to automation.

The goal of the A/B test is to determine which promotion theme "generates the most website visits." The Click-through rate (CTR) is the metric that directly measures this outcome. CTR is calculated as the percentage of email recipients who clicked on a link within the email. A higher CTR indicates that the email's content and call-to-action were more effective at compelling users to click through to the website, directly fulfilling the campaign's objective.

B. Lowest unsubscribe rate: This metric measures audience retention and list health, not the effectiveness of a promotion in driving website traffic.
C. Highest open rate: This metric primarily reflects the effectiveness of the subject line and sender recognition, but it does not measure engagement with the content that leads to a website visit.
D. Lowest activity rate: A low activity rate would signify poor performance. A winning promotion would be indicated by the highest activity rate, not the lowest.

1. Adobe Campaign Classic v7 Documentation, Key performance indicators (KPIs): This document defines the Click-through rate as the primary indicator of the targeted population's reactivity to the message content. It states, "This is the main indicator for measuring the effectiveness of a message and the interest that recipients have in it."

Reference: Adobe Experience League. (n.d.). Key performance indicators. Adobe Campaign Classic v7 Documentation. Retrieved from https://experienceleague.adobe.com/docs/campaign-classic/using/reporting/indicator-calculation.html?lang=en#key-performance-indicators (See section: "Key performance indicators").

2. Adobe Campaign Standard Documentation, Delivery summary report: This official guide defines the core metrics for email campaigns. It defines "Click" as the "Number of persons who clicked in a content" and "Click-through rate" as the "Ratio of the number of clicks to the number of successful deliveries." This directly links the metric to the action of visiting the website via a content link.

Reference: Adobe Experience League. (n.d.). Delivery summary report. Adobe Campaign Standard Documentation. Retrieved from https://experienceleague.adobe.com/docs/campaign-standard/using/reporting/about-reporting/delivery-summary.html?lang=en (See section: "List of components" under "Delivery statistics").

3. Adobe Campaign Classic v7 Documentation, A/B testing: The documentation on A/B testing explicitly lists "best click-through rate" as a potential winning strategy. This confirms its role as a decisive metric for determining the most effective version of a campaign based on user interaction with the content.

Reference: Adobe Experience League. (n.d.). A/B testing. Adobe Campaign Classic v7 Documentation. Retrieved from https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/defining-the-audience/a-b-testing.html?lang=en (See section: "Defining the winning strategy").

The email preview functionality in Adobe Campaign Classic is a critical pre-send step that allows a user to visualize how the email will appear to a specific recipient. This process directly enables the testing of personalization by populating the email with a selected recipient's data to ensure dynamic content renders correctly. The preview also displays the full email content, which includes embedded links. This allows for the verification of the mirror page link and the legally mandated opt-out link, ensuring they are present, correctly formatted, and functional before the campaign is executed.

C. spam score: Spam score analysis is a separate pre-send check performed via a distinct tool (e.g., SpamAssassin integration), not within the visual preview rendering of the email content.

1. Adobe Campaign Classic v7 Documentation - Previewing messages: "The Preview tab lets you view the rendering of each message for a recipient of the target. This allows you to check the personalization data and the general aspect of your message before sending the proofs or the final delivery." This source confirms that personalization (B) is a primary function of the preview. The preview renders all content, which includes mirror page (A) and opt-out links (D), making them verifiable.

Source: Adobe Experience League, Adobe Campaign Classic v7 Documentation, Section: Prepare and send messages > Previewing messages.

2. Adobe Campaign Classic v7 Documentation - Unsubscription: "The unsubscription link is mandatory in the emails and is added by default in the templates." The presence and functionality of this mandatory link (D) are verified during the content preview and proofing stage.

Source: Adobe Experience League, Adobe Campaign Classic v7 Documentation, Section: Get started with channels > Email channel > About unsubscription.

3. Adobe Campaign Classic v7 Documentation - Checking the spam score: "To start the spam score computation, open a delivery and click the Spam & Litmus button... This action is available in the delivery's action bar." This documentation explicitly describes the spam score check (C) as a separate action initiated from the delivery's action bar, distinct from the preview tab.

Source: Adobe Experience League, Adobe Campaign Classic v7 Documentation, Section: Prepare and send messages > Content validation > Checking the spam score.

The most efficient method is to use the built-in Control group activity. This activity is specifically designed for creating control populations using various methods, including stratified sampling. By configuring the activity to use "Random sampling" and enabling "Data grouping" on the 'age group' field, the system will automatically take a 10% random sample from within each distinct age group present in the inbound population. This approach is highly efficient as it accomplishes the complex task of stratified sampling in a single, purpose-built workflow activity, making it scalable and easy to configure.

A. This method is less efficient because it requires a second, complex query activity with ranking functions to correctly select a random percentage from each subgroup, adding unnecessary complexity.
B. This option is incorrect because it is too vague. It describes an outcome (excluding the control group) but fails to specify the actual method for creating the stratified sample.
C. Using a Split activity is inefficient and not scalable. It would require the practitioner to manually create a separate output branch for every single age group, which is cumbersome and difficult to maintain.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Control group" activity:

Section: Data grouping tab

Content: "The Data grouping tab lets you create control groups on data groups. This lets you apply random sampling on a certain number of records belonging to the same group. For example, you can extract 10 recipients per zip code." This directly confirms that the Control group activity is the designated tool for stratified sampling (sampling within groups), which is the core requirement of the question.

2. Adobe Experience League - Campaign Classic v7 Documentation, "Split" activity:

Section: Configuration

Content: The documentation shows that the Split activity is used to create multiple, distinct subsets based on defined criteria. While random sampling can be applied to a subset, it would require creating a separate subset for each age group, confirming that this method is less efficient than the Control group activity's data grouping feature for this specific scenario.

To test all variations of conditional content in an Adobe Campaign delivery, the Business Practitioner needs methods that allow for systematic checking against different recipient profiles.
1. Proof with a defined proof target: A specific target group can be created for proofing, containing recipients from each required segment. Sending a proof to this target ensures each member receives the content variant corresponding to their profile data.
2. Proof with Seed address: Seed addresses can be configured to substitute their data with that of a profile from the main target. By creating multiple seed addresses and linking each to a profile from a different segment, all content variations can be sent for review.
3. Proof with Substitution of address with a fixed profile: This allows sending a proof to any email address while using the personalization data from a specific, hand-picked profile from the target audience. This process can be repeated for a profile from each segment to validate all content variations.

C. Proof with Substitution of address with a random profile: This method is not suitable for systematically covering all variations, as the profile used for personalization is chosen randomly. It is useful for spot-checking but does not guarantee that every segment's content will be tested. ---

1. Adobe Campaign Classic v7 Documentation - Sending Proofs: This document outlines the various methods for sending proofs.

For option A (Defined proof target): Under the section "Defining the proof recipients," it states, "You can select the proof recipients explicitly, define them using a filtering rule, or create a specific group." This supports creating a targeted group with members from all segments.

For option D (Substitution with a fixed profile): The section "Substitution of the address" describes the process: "Select a recipient from the delivery target and send the proof to a substitute address." This directly corresponds to using a fixed profile for personalization.

For option C (Incorrect): The same "Substitution of the address" section also mentions the random option: "Select a random recipient from the delivery target...". As explained, this does not guarantee full coverage.

2. Adobe Campaign Classic v7 Documentation - Using Seed Addresses: This page details the functionality of seed addresses.

For option B (Seed address): The section "Substitution of a seed address" explains, "You can substitute a seed address with the data of a profile from the delivery target... This lets you use a seed address to test the personalization of a delivery." This confirms that seed addresses can be used to test content for specific profiles, and by extension, for profiles in different segments.

Before adding a Delivery activity to a campaign workflow, a practitioner must first determine the communication channel (e.g., email, SMS, push notification). This decision is fundamental as it dictates the type of Delivery activity to use and which delivery template to select during configuration. The channel choice is a primary strategic step that precedes the tactical configuration of targeting, content, and template selection within the workflow activity itself. The user interface for adding a delivery requires selecting a template, and templates are inherently channel-specific.

B. target: The target population is typically defined by preceding activities in the workflow, such as a Query or Union, and is passed as an input to the Delivery activity.
C. template: A specific template is selected during the configuration of the Delivery activity, not before. The choice of template is a direct consequence of the pre-determined channel.
D. content: The content (e.g., subject line, HTML body) is created and configured within the Delivery activity after it has been added to the workflow and its template has been selected. ---

1. Adobe Experience League, Campaign Classic v7 Documentation, "Delivery (workflow activity)": In the overview section, the documentation states, "When you add a delivery activity, you must select the delivery channel and define its content and target." This explicitly lists selecting the channel as a required step when adding the activity. (See: Adobe Campaign Classic Documentation > Workflows > Workflow activities > Actions > Delivery).

2. Adobe Experience League, Campaign Classic v7 Documentation, "Get started with workflows": The tutorial for creating a campaign workflow demonstrates the process of first defining a target with a query, and then adding an "Email delivery" activity. This illustrates that the choice of channel ("Email") is a distinct, primary step in the workflow's design. (See: Adobe Campaign Classic Documentation > Get Started > Get started with workflows > Build a targeting workflow).

3. Adobe Experience League, Campaign Classic v7 Documentation, "About channels": This section details the various communication channels available in Adobe Campaign. The entire delivery creation and configuration process is predicated on the initial selection of one of these channels, reinforcing its foundational importance. (See: Adobe Campaign Classic Documentation > Channels > About channels).

The discrepancy between the upstream population (initial target) and the final sent count in Adobe Campaign Classic is typically due to exclusions applied during the delivery analysis phase. Pressure typologies are rules designed to prevent over-solicitation by excluding recipients who have been contacted too frequently, thus reducing the final count. Similarly, recipients whose addresses are on the quarantine list due to previous delivery failures (e.g., hard bounces) are automatically excluded from the delivery, further lowering the number of messages sent compared to the initial target audience.

A. The upstream population did NOT include seeds. Seed addresses are added to the target audience for testing and validation; their absence would not decrease the sent count relative to the primary population.
D. The upstream population was too large. While a very large population can impact performance, its size is not a direct filtering criterion that would inherently cause the sent count to be lower.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Pressure rules": This document explains how pressure rules work. It states, "Pressure rules are used to avoid over-soliciting a recipient. Depending on the settings, recipients will be excluded from the delivery if they have already been sent a certain number of deliveries..." This directly supports that applying pressure rules reduces the final sent count. (Found in Campaign Classic v7 > Delivery > About typology rules > Pressure rules).

2. Adobe Experience League - Campaign Classic v7 Documentation, "Quarantine management": This source details the quarantine mechanism. It specifies, "An address that is in quarantine will be excluded by default during delivery analysis and will not be targeted by the delivery." This confirms that quarantined recipients are removed from the send, causing the sent count to be lower than the initial population. (Found in Campaign Classic v7 > Delivery > Understanding delivery failures > Quarantine management).

3. Adobe Experience League - Campaign Classic v7 Documentation, "Delivery analysis": This section describes the steps before a delivery is sent. It notes, "During this phase, the target population is calculated, and the message content is prepared for each recipient... The delivery analysis logs show the number of messages to be sent after exclusions." This confirms that exclusions, such as those from typologies and quarantines, occur during analysis. (Found in Campaign Classic v7 > Delivery > Get started with deliveries > Steps for sending a delivery > Delivery analysis).

The Data extraction (file) activity is the designated tool within Adobe Campaign Classic workflows for exporting data. Its primary function is to take the data from the inbound transition (the workflow's temporary table) and write it to an external file. This activity allows for detailed configuration of the output file, including its format (e.g., CSV, TXT), the specific columns to be extracted, sorting order, and destination path, making it the correct choice for data export operations.

A. Data download: This is not a standard activity name. The "File download" activity imports a file from an external source into the workflow, which is the opposite of exporting.
B. List update: This activity is used to add, update, or remove data from a predefined list within the Adobe Campaign database, not to export data to an external file.
C. Update data: This activity performs mass update operations on records already existing within the Adobe Campaign database; it does not create an external data file.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Data extraction (file)": This official documentation explicitly states, "The Data extraction (file) activity is a data management activity that lets you extract data from the database into a file." (Section: Data management activities).

2. Adobe Experience League - Campaign Classic v7 Documentation, "List update": This source describes the activity's function: "The List update activity lets you update an existing list." It does not mention exporting data. (Section: Targeting activities).

3. Adobe Experience League - Campaign Classic v7 Documentation, "Update data": This document clarifies the purpose of this activity: "The Update data activity is a data management activity that lets you perform a mass update on the fields of a database table." (Section: Data management activities).

4. Adobe Experience League - Campaign Classic v7 Documentation, "File download": This document details the function of the "File download" activity, which is to "download a file from an explicit URL or an URL calculated from the events of the transition." This confirms its role is for data import, not export. (Section: File transfer activities).

The standard and intended method for manually adding a single recipient within the Adobe Campaign client console is through the dedicated user interface. A Practitioner navigates to the 'Profiles and Targets' folder, selects the 'Recipients' node, and then uses the 'Create' or 'New' button. This action opens the 'Recipients' form, which is specifically designed for entering and managing the attributes of a new profile, such as name, email, and other custom fields. This ensures data is entered correctly according to the form's logic and structure.

A. The 'Edit' tab of a schema is used to define or modify the underlying XML structure and database table columns, not to add data records.
B. The 'Import Package' functionality is for migrating platform configurations (like schemas, forms, and workflows) between different Adobe Campaign instances, not for data import.
C. The 'Data' tab of a schema displays the raw data within the table; it is primarily for viewing and is not the standard user interface for creating new profiles.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Creating profiles": This official guide explicitly states the procedure: "To create a profile, click the Profiles and Targets link in the navigation pane and click the Recipients link. Click the Create button." This directly corresponds to option D. (See the section "Creating a profile" under "Profiles and audiences").

2. Adobe Experience League - Campaign Classic v7 Documentation, "Data schemas": This document describes the function of the schema's 'Edit' tab: "The Edit sub-tab contains the XML source code of the schema." This confirms that this tab is for structural definition, not data entry, making option A incorrect. (See the section "Editing schemas").

3. Adobe Experience League - Campaign Classic v7 Documentation, "Package exports and imports": This source details the use of packages for configuration management: "Packages let you export and import a set of Adobe Campaign objects to move a configuration from one Adobe Campaign instance to another." This validates that option B is incorrect for adding recipients. (See the "Operating principle" section).

The total number of records is determined by the behavior of each delivery type over the three-week period. Recurring Delivery: A recurring delivery creates a new, distinct delivery instance (a new record in the nms:delivery table) each time its associated scheduler or workflow executes. Since the scheduler runs weekly for three weeks, this will create 3 delivery records. Continuous Delivery: A continuous delivery creates only 1 single delivery record upon its initial creation. Subsequent executions of the triggering workflow do not create new delivery records; instead, they add new recipients to the target of this single, ongoing delivery. Therefore, the total number of records created is 3 (from recurring) + 1 (from continuous) = 4.

B. 2: This incorrectly assumes only one record is created for the recurring delivery and one for the continuous delivery, ignoring the weekly schedule.
C. 6: This incorrectly assumes that the continuous delivery behaves like a recurring delivery, creating a new record each week (3+3).
D. 3: This incorrectly omits the single record created for the continuous delivery, only counting the records from the recurring delivery.

1. Adobe Experience League. Campaign Classic v7 Documentation, "Recurring delivery".

Section: About recurring deliveries.

Content: "Each time it is executed, a new delivery is created from the template and the delivery code is calculated based on the template's delivery code, to which the date and time of execution is added." This confirms that each weekly run generates a new delivery record.

2. Adobe Experience League. Campaign Classic v7 Documentation, "Continuous delivery".

Section: About continuous deliveries.

Content: "A continuous delivery lets you add new members to a delivery that has already been sent... Unlike a standard delivery, a continuous delivery does not have a pre-calculated target. The target is built as and when new contacts are added." This establishes that it is a single delivery entity that is updated, not re-created.

3. Adobe Experience League. Campaign Classic v7 Documentation, "Scheduler".

Section: Properties of the activity.

Content: "The Scheduler activity lets you schedule the execution of a branch of a workflow." This confirms the scheduler's role is to trigger the downstream activities (the deliveries) at the specified frequency.

In an Adobe Campaign workflow, the 'Split' activity is used to divide a population into multiple subsets based on defined criteria or percentages. When the "Generate complement" option is selected for this activity, it creates an additional outbound transition. This specific transition isolates the remainder of the population—that is, all the records that did not meet the criteria for any of the primary subsets. The primary purpose of this complement is to allow the business practitioner to analyze, count, or target this remaining group separately.

A. The order of selection is configured within the split activity's properties, not analyzed by the compliment, which only captures the final remainder.
C. "Rejected records" usually implies data that failed processing or delivery, whereas the compliment contains valid records that simply did not match the split criteria.
D. The split activity segments the target audience (records/profiles), not the creative content. Content is handled in subsequent workflow activities like deliveries.

1. Adobe Experience League - Campaign Classic v7 Documentation: In the section describing the 'Split' activity, the "Generate complement" option is detailed. It states: "Adds an output transition to the split activity named 'Complement'. This transition contains the population that was not selected in the other transitions." This directly supports that the compliment is for analyzing the remaining records.

Source: Adobe Experience League, Campaign Classic v7 Documentation, "Split" activity.

Section: Properties > Generate complement.

In Adobe Campaign Classic, the "Update list" workflow activity is used to create or update a list of recipients. To append new records to a list that already exists, the practitioner must configure the activity's execution options. The key setting is the "Purge list if it exists" checkbox. By unchecking this option, the workflow will add the incoming records to the end of the existing list. If this option is checked, the workflow will first delete the existing list and then create a new one with only the incoming records, which is not the desired behavior for appending.

A. Only create new lists and avoid updating an existing list: This is a workaround that fails to meet the requirement of appending records to an existing list.
C. Specify the name explicitly in the options: While specifying the list name is required to identify the target list, it does not control the update behavior (append vs. purge).
D. Store the list on an external database: The storage location of the list (internal or external) is irrelevant to the logic of how the "Update list" activity appends or purges records.

1. Adobe Experience League, Campaign Classic v7 Documentation, "Update list". This official documentation describes the activity's properties. In the "Execution" section, it details the "Purge list if it exists" option: "If this option is unchecked, the content of the list is added to the existing list. If the list does not exist, it is created." This directly supports the correct answer. (Accessed under Workflow activities > Targeting activities > Update list).

The most effective method to ensure all deliveries based on a specific template are stored in a designated folder is to configure the "Execution folder" within the delivery template's properties. When a delivery is created from this template, it inherits this setting, and Adobe Campaign automatically saves the delivery instance in the specified folder. This automates the process, ensures consistency, and eliminates the potential for human error associated with manual folder management.

A. Define Routing within the delivery properties of each delivery template. Routing properties in a delivery template are used to manage technical sending parameters, such as assigning deliveries to a specific IP address pool (affinity), not for defining the storage folder within the Campaign Explorer.
B. Move all deliveries manually into defined folders. This approach is inefficient, prone to user error, and not scalable. The question asks for the "most effective" implementation, which implies an automated and reliable solution, not a manual one.
C. Modify the delivery mapping to define the routing. Delivery mappings (nms:deliveryMapping) are technical schemas used to configure how incoming messages (e.g., replies, bounces) are processed and linked to the original delivery, not for determining the storage location of the delivery object itself.

1. Adobe Campaign Classic v7 Documentation - Delivery templates: In the section describing the properties of a delivery template, the "Execution folder" is detailed. "This field lets you select the folder in which the deliveries created from this template will be executed and stored." This directly supports the correctness of option D. (See Adobe Experience League: Campaign Classic v7 Documentation > Campaigns > Deliveries > About delivery templates > Properties of a template > Advanced parameters).

2. Adobe Campaign Classic v7 Documentation - Delivery properties: The documentation on delivery properties explains the function of "Routing". "The routing field lets you select the delivery's management mode: Email, Mobile (SMS or WAP Push), etc. By default, deliveries are managed by the Adobe Campaign MTA (Message Transfer Agent). You can select an external account for sending deliveries." This confirms that routing is unrelated to folder storage. (See Adobe Experience League: Campaign Classic v7 Documentation > Campaigns > Deliveries > Delivery properties > To parameters).

When an Adobe Campaign workflow successfully completes and reaches the 'Finished' state, it signifies that all its constituent activities have been executed and the final cleanup processes have occurred. For a workflow within a campaign context ("campaign workflow"), its primary purpose is typically to orchestrate and send marketing communications. Therefore, the successful completion implies that any delivery activities within it have been processed and sent. Concurrently, a mandatory part of the workflow finalization process is the cleanup of temporary resources, which includes dropping the worktables created during its execution to maintain database health.

C. The campaign state has changed to Finished. The parent campaign's status is managed separately from its workflows. A campaign might have multiple workflows or other conditions (like end dates) that determine its final state.
D. The approval steps have been approved. Approval steps are optional activities. A workflow can be designed and successfully executed without containing any approval steps, so this is not a mandatory occurrence.

1. Adobe Campaign Classic v7 Documentation, "Workflow properties": In the 'Execution' tab of a workflow's properties, the option "Keep the result of temporary tables" is detailed. By default, this is unchecked, meaning "the worktables are dropped at the end of the execution." This confirms that dropping temporary tables is a standard task for a finished workflow. (See section: Workflows > Get started with workflows > Workflow properties).

2. Adobe Campaign Classic v7 Documentation, "About campaigns": This section defines a campaign as a tool to "coordinate a set of marketing actions (deliveries, creation of files, etc.)." A workflow created within this context is the mechanism to execute these actions. This supports the premise that for a "campaign workflow" to be considered finished, its core marketing action, the delivery, must have been sent. (See section: Campaign Management > Get started with Campaign Management > About campaigns).

3. Adobe Campaign Classic v7 Documentation, "Campaign statuses": The documentation explains that campaign statuses can be updated manually or via the "Update campaign status" technical workflow, which runs on a schedule. This confirms that a campaign's status is not directly and immediately altered by the completion of a single targeting workflow. (See section: Campaign Management > Get started with Campaign Management > Campaign statuses).