> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/campaign-influences/campaigninfluencesenable.md).

# CampaignInfluencesEnable

**CampaignInfluencesEnable** template enables the opportunity detail page or the API to create, retrieve, update, or delete campaign influence records.

To create this template, follow the steps below:

1. Log in to your AutoRABIT account.
2. Click on the **Env. Pro.** module.
3. Click on **Create New Template**.
4. Go to the **Create** [**Unsupported Metadata Template**](/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates.md) tab.
5. Provide a **template name** and a **short description**.
6. Select the **CampaignInfluencesEnable** checkbox under **Campaign Influences**.
7. Click **Add**.
8. On the next screen, a **Test Case Name** will appear automatically by default. To add custom test data, click **Add**. Once complete, click **Save** to store the configuration.
9. Click **Save** again to finalize the template.
10. Upon successful creation, you'll be redirected to the **Environment Provisioning History** screen.
11. Click the **Run** button to execute the template on your destination org.
12. Select your **destination org** from the dropdown and enter the **email address(es)** to receive run notifications.
13. In the **Post Deployment Steps**, select the test cases you recently created.
14. For a detailed summary of the executed operation, visit the **View History** page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/campaign-influences/campaigninfluencesenable.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.