# \[Troubleshooting] My modifications are not displayed
## 🛠️ \[Troubleshooting] My modifications are not displayed
This article explains the common causes of the problem and provides solutions to minimize or eliminate this issue.
### Verify the targeting conditions
If you have made one or more modifications to an element of your page in the visual editor, and they don’t appear when performing the QA of your campaign, the first step is to **verify that you are assigned to the variation including the change(s) you’ve made.**
To verify that you are assigned to the campaign and to the variation, use one of the 2 methods explained in [Checking if a page is assigned to a campaign](/help-center/troubleshooting/troubleshooting-checking-if-a-page-is-assigned-to-a-campaign.md):
* **The QA Assistant**
* **The web browser’s tool**
### If you are not assigned to the variation
If you are not affected by the variation (rejected), you won’t be able to see any modifications made to this variation, as you don’t meet the targeting conditions of the campaign.
In the table below, you can see every reason you may not be accepted to the test:
| **Status** | **Explanation** |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **“accepted”** | You are seeing the test named above. |
| **“target\_pages\_rejected”** | You do not meet the targeting conditions configured on the targeting page. |
| **"audience\_rejected"** | You were rejected from a specific test because you do not match the targeting criteria for the campaign. To see which targeting criteria you do not match, click the **targeting** object below in the console. Each targeting criterion added to the campaign is listed in that object and will display **true** if you match the criterion or **false** if you don’t match it. |
| **“trigger\_rejected”** | You do not meet the targeting conditions of the trigger configured on the targeting page. Check what trigger has been set up to ensure you assign yourself to it correctly. |
| **“pending”** | Targeting is set with **AJAX mode** and is waiting for the element to be present on the page before applying. Alternatively, targeting includes geolocation, IP, weather, browser, device, or DMP criterion which has not yet been found. |
| **“qa\_parameters\_rejected” or “QA rejected”** | You do not meet the conditions configured in QA mode (IP address or cookie). Ensure the IP address entered is yours or that you have added the targeted cookie. Otherwise, refresh the tag and retry in a new incognito window (make sure to close all other browser windows). |
| **“master\_campaign\_not\_checked”** |
In personalizations or multipage tests that contain scenarios or subtests, there are two types of ID:
The ID of the global test, which will always be rejected
The ID of each subtest or scenario (which will usually be the global ID + 1 (e.g. if the global test ID is 675391, each subtest will have an ID of 675392, 675393, 675394, etc.)
Check the subtest ID because the global ID will always have the status "master\_campaign\_not\_checked".
|
The "Force display" option in the QA Assistant is designed to ensure your campaign reaches the intended audience regardless of predefined constraints. By using this feature, it allows you to override the usual targeting rules, making it easier to test or showcase your campaign without any restrictions. Be cautious when using this option as it may lead to unintended exposure beyond the target audience, affecting overall campaign metrics.
### If you are assigned to the variation
**If you are assigned to the variation** (not the original version) **but still can’t see the modifications**, it means that the issue comes from the modifications that have been made via the editor. This may be because there are too many modifications in the variation, or you used the **Edit HTML** option.
If so, remove unnecessary modifications from the **Active changes** panel and keep only the relevant ones. If the problem persists, some modifications may have been made to a selector that no longer exists on the page. You can check the selector used by clicking the modification, then **Change selector**.
If you find that modifications have been made to a selector that no longer exists on the page, update the selector so that it matches an existing element of the page.
{% hint style="info" %}
**Good to know đź’ˇ**
Update the AB Tasty tag after each modification you make on a live campaign. This allows the changes to be taken into account in the production phase.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.abtasty.com/help-center/troubleshooting/troubleshooting-my-modifications-are-not-displayed.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.