Request Management uses request forms to collect, review, and approve campaign requirements before execution. Request Management supports the direct creation of Paid Initiatives, Ad Sets, and Ad Variants from approved Build Your Own Request Forms. This capability extends the existing entity creation workflow by allowing paid entities to be created directly from requests. To learn about requests and request forms, see What are Requests and Request Forms.

Use this workflow to streamline the transition from approved requests to paid execution by creating paid entities directly from requests.

Before you begin

Before you create a Paid Initiative from a request:

• Ensure that the request is submitted through a Build Your Own Request Form and is available in Request Management. To create a request form, see Create New Request Forms.

• To automatically populate the values from a request form during campaign creation, configure Paid Pre-Publishing Rules before initiating the workflow.

How it works

The following process creates paid entities from approved requests and populates them with request form data:

1. A user submits a request through a Build Your Own Request Form.

2. The request is approved and becomes available in Request Management.

3. Paid Pre-Publishing Rules map request form fields to Paid Initiative, Ad Set, or Ad Variant fields.

4. A user creates paid entities from the approved request.

5. The mapped request data populates supported fields during entity creation.

6. The created entities remain associated with the originating request for traceability and reporting.

After creation, the request and the paid entities remain associated so that users can trace the originating request from Request Management and Ads Manager.

Configure request-to-entity field mappings

Use Paid Pre-Publishing Rules to populate Paid Initiative, Ad Set, and Ad Variant fields from request responses. Configure the mappings before users create Paid Initiatives from approved requests.

For example, you can map the start date, end date, and budget from a request form to the corresponding Ad Set fields. To learn more about Paid Pre-Publishing Rules and how to access Rule Engine, see Paid Pre Publishing Rule Conditions & Actions.

1. Open Rule Engine and create a new Paid Pre-Publishing Rule or open an existing rule.

2. Set Context to Paid Pre Publishing and complete the required rule details.

   

3. Configure the rule to trigger when a user creates a Paid Initiative from a request.

4. Under Actions To Copy properties from source to destination, select Request Form as the source and select the destination entity that you want to populate:

   • Paid Initiative

   • Ad Set

   • Ad Variant

     

5. Click + Add Fields and map the request form field to the corresponding destination field. Request form sources can include:

   • Standard fields added to the request form.

   • Custom fields from the Request Forms asset type.

   Standard source fields appear with the request form name appended to the field name.

6. Select a mapping operator:

   • Set

   • Set if Absent

7. Repeat the mapping process for each field that you want to populate.

   Note: You cannot select the same source field more than once within the same rule

8. Click Save.

Supported destination fields

You can map request form fields to the following standard destination fields.

You can also map custom fields for Paid Initiatives, Ad Sets, and Ad Variants.

Create a Paid Initiative from a Request

After you configure the required field mappings and the request is approved, create the Paid Initiative.

1. Open Production Dashboard > Request Management. The Request Management dashboard opens.

2. Locate the approved request that was submitted through a Build Your Own Request Form.

3. Click the request menu and select Associate an Entity.

   

4. In the Associate an Entity window:

   • Select Paid Initiative as the Entity Type.

   • Select the Ad Account that you want to use and click Done.

   Ads Composer opens and applies the configured field mappings.

   

5. Review the values populated from the request response and verify that the expected request values appear in the mapped Paid Initiative, Ad Set, and Ad Variant fields.

6. Enter the required Paid Initiative, Ad Set, and Ad Variant details. You can create all three entities within the same Ads Composer workflow.

7. Review the QA checklist configured for the selected ad account before creating the entities.

8. Complete the remaining steps in Ads Composer to create the entities.

Verify request associations

1. Navigate to the request in Request Management and open the request details pane.

   

2. Select Associated Entities and verify that the newly created Paid Initiative appears in the Paid Initiatives section.

   Note: If more than five Paid Initiatives are associated with a request, the section displays them in a collapsible view.

   

3. Review the available details, including Objective, Flight Date, and Status.

4. Click View in Ads Manager to open it in Ads Manager.

5. If required, dissociate the Paid Initiative from the request.

   Note: If you dissociate a Paid Initiative from its request, the Request Form column in Ads Manager no longer displays the associated form name.