> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runalloy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plobal

> Integration details and setup guide for the Plobal connector in Alloy Automation.

## Pre-Built Tooling

| Category                            | Details                        |
| ----------------------------------- | ------------------------------ |
| **Authentication**                  | API Key (Header: X-plobal-key) |
| **Two-Way Sync**                    | No                             |
| **Events Supported**                | No                             |
| **Realtime**                        | Polling                        |
| **Supports Rate Limiting**          | Yes                            |
| **Authentication Scopes Supported** | N/A (API Key)                  |

***

## Objects Supported

Alloy Automation supports syncing the following objects from **Plobal**:

* **Mobile App Users**
* **Push Notifications**
* **App Analytics**
* **User Engagement Data**

***

## Set Up Guide

### Trial Access

| Question                                           | Answer                                                                                                                  |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Offers free trial?**                             | Yes. Plobal offers demo and trial access for mobile app features. [Request demo](https://www.plobalapps.com/contact-us) |
| **Requires paid sandbox?**                         | No. Contact Plobal for trial account setup.                                                                             |
| **Requires partnership to obtain authentication?** | No. However, you need to have a Plobal Apps account to access API features.                                             |

***

### Authentication (API Key)

For customers who want to completely whitelabel their authentication experience, you can provide your own developer keys instead of using Alloy Automation's.

<steps>
  <step title="Create Plobal Account">
    Sign up for Plobal Apps at [https://www.plobalapps.com](https://www.plobalapps.com) or contact their sales team to set up an account
  </step>

  <step title="Access Integration Settings">
    1. Log in to your Plobal Apps dashboard
    2. Navigate to **Settings** or **Integrations**
    3. Look for **API Keys** or **Alloy Integration** section
  </step>

  <step title="Generate API Key">
    1. Click on **Generate API Key** or **Create New Key**
    2. Provide a descriptive name for the integration (e.g., "Alloy Automation")
    3. Copy the generated API key (labeled as X-plobal-key)
    4. Store the key securely
  </step>

  <step title="Configure in Alloy Automation">
    1. In Alloy Automation, enter your Plobal API key
    2. The key will be sent in the `X-plobal-key` header for all API requests
    3. Test the connection to verify authentication
  </step>
</steps>

For more information, visit the [Plobal Alloy Integration page](https://www.plobalapps.com/integration/alloy/).

***

## Use Cases

### 1) Mobile app user synchronization

Sync mobile app user data from Plobal to your CRM or customer data platform to create a unified view of customers across web and mobile channels.

### 2) Push notification automation

Trigger personalized push notifications through Plobal based on events in your e-commerce platform, such as abandoned carts, order shipments, or back-in-stock alerts.

### 3) Mobile engagement analytics

Pull app analytics and user engagement data from Plobal into your business intelligence platform to measure mobile app performance and ROI.

### 4) Cross-channel marketing

Coordinate marketing campaigns across email, SMS, and push notifications by integrating Plobal with your marketing automation platform for consistent messaging.

### 5) Mobile app personalization

Use customer data from your e-commerce platform to personalize the mobile app experience in Plobal, including product recommendations and custom content.

***

## API Gotchas

* **API key header format:** Plobal uses a custom header name `X-plobal-key` for authentication. Ensure your HTTP client is configured to send the API key in this specific header.

* **Limited documentation:** Plobal's public API documentation may be limited. Contact Plobal support for detailed API specifications and endpoint documentation if needed.

* **Platform-specific features:** Some Plobal features may be specific to iOS or Android platforms. When working with mobile app data, be aware of platform-specific fields and behaviors.

* **Rate limiting:** Implement proper rate limiting and retry logic to avoid API throttling during high-volume operations.

> For questions or troubleshooting, contact **[support@runalloy.com](mailto:support@runalloy.com)**.