# AdMob

### Recommended Setup:

Use this action to serve ads at appropriate moments, such as at page load, after completing tasks, or between app transitions.

<figure><img src="https://46162361-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbRbEDU7JrvMAgg52AY%2Fuploads%2FRpMm178IofRWdPTklxau%2FScreenshot%202025-01-03%20at%204.57.54%E2%80%AFPM.png?alt=media&#x26;token=16e40697-a50f-4031-9d35-a9d64ad16131" alt=""><figcaption></figcaption></figure>

### Steps:

1. Go to the Workflow tab and select the event trigger
   * Example triggers include page load, button clicks, or after completing a user action.
2. Add the AdMob action
   * Drag the action into your selected workflow.
3. Configure the following properties:
   * **Ad Type**: Choose the type of ad to display:
     * `banner`: For static banner ads displayed at the top or bottom of the screen.
     * `fullScreen`: For immersive, full-screen ads that appear during transitions or breaks.
     * `rewards`: For reward-based ads, where users earn incentives for viewing.
   * **Ad ID**: Enter the AdMob ad unit ID for the selected ad type.

### Callback Data

* **State**: The callback response from `fullScreenAd` or `rewardsAd` is stored in the **init-webtonative's** element states **Ad Mob Response Fullscreen** and **Ad Mob Response Rewards**.
* **Access**: Use these states in subsequent workflows to check ad status or handle user interactions (e.g., granting rewards).