---
schema_version: "1"
id: 43732c3accb15fcd6366dd4546806a32cfd6ed48cb2b688c6cb2cf6f0fb217e1
title: Testing an Activation Platform Package
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_test_your_new_activation_platform_package.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_test_your_new_activation_platform_package.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 34f81a70c1cd61504bef7dc2151cfd6f2422be27dbb6cc2d77d585f565bae978
description: Test an activation platform package by installing it either in an Enterprise or Developer Edition org that has a provisioned Data 360 license. For more rapid testing and inspection of file outputs as you develop your app, use a Dev org to trigger manual activation publish. When testing your activation platform app in an Enterprise org, activation files are published every 24 hours if the activation output is grouped by user identifiers (PER_USER). If the activation output is grouped by segments (PER_SEGMENT), the refresh schedule is tied to the segment publish schedule.
products:
  - Data 360
release: "264"
---
# Testing an Activation Platform Package

Test an activation platform package by installing it either in an Enterprise or Developer Edition org that has a provisioned Data 360 license. For more rapid testing and inspection of file outputs as you develop your app, use a Dev org to trigger manual activation publish. When testing your activation platform app in an Enterprise org, activation files are published every 24 hours if the activation output is grouped by user identifiers (PER\_USER). If the activation output is grouped by segments (PER\_SEGMENT), the refresh schedule is tied to the segment publish schedule.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr></tbody></table>

- **[Use a Package Subscriber Org for Testing](https://help.salesforce.com/s/articleView?id=data.c360_a_use_package_subscriber_for_testing.htm&release=264.0.0&type=5)**  
    When using a Developer edition org in the context of a packaged app, Salesforce uses the terms Packaging org and Package Subscriber org. The Packaging org is where the package is created. The Package Subscriber org is an org that has installed a package from a Packaging org. To speed up testing, developers can now install their package in another Dev org and manually trigger an activation publish.
- **[Use a Package Subscriber Org to Trigger a Publish](https://help.salesforce.com/s/articleView?id=data.c360_a_trigger_a_manual_publish.htm&release=264.0.0&type=5)**  
    To speed up testing, use the package subscriber org and manually trigger an activation publish to inspect and validate the output files.