Does "Development" Status of Adobe Launch Tag Property Prevent Data Flow to Production Report Suite?

[jaishal]

We are implementing the AEP Mobile SDK in our mobile app and have configured the app to use the Production environment App ID from Adobe Launch (i.e., configureWithAppId() is correctly set with the Production ID).

However, the Launch tag property is still in "Development" status — it has not yet been published to Production.

Our main question is:
Does having the tag property in an unpublished “Development” state prevent the SDK from successfully sending data to the Production Adobe Analytics report suite — even if the Production environment App ID is used in the app?

We are currently seeing "unspecified" or missing data in the Production report suite, and suspect that the unpublished Production environment may be the cause.

Please confirm how the Launch publishing status affects mobile SDK behavior and data flow to report suites.

[pradnya_balvir]

Hi @jaishal ,

No, the tag property's "Development" status in Launch does not block data from being sent to the Production Adobe Analytics report suite, as long as your app is configured to use the Production environment’s App ID (configureWithAppId() is set correctly).

To enable full data flow:

1. Go to Adobe Launch > your tag property.

2. Make sure all required configurations (rules, extensions, etc.) are in place.

3. Publish the changes to the Production environment.

4. Then test again in the app (with the Production App ID).

Once published:

• The SDK will be able to download the Production config from Launch.

• Data will flow to the correct Production Adobe Analytics report suite (assuming the Launch rule and extension settings are correct).

Thanks.

Pradnya

[HarveerGi]

Hi @jaishal ,

Using prod app id in your app doesn't collect any data unless you have you configured extensions (and rules if needed) built to the production environment in Launch, no matter if you have anything built under development environment in Launch or not.

Cheers!

[Vinay_Chauhan]

Hi @jaishal 

If your app is configured with the Production App ID, technically the SDK will try to pull the config and send data. But if the Production environment in Launch hasn’t been published yet, there's a high chance that the SDK is either getting no config (404) or pulling an older, stale config.

In that case, even though things seem wired correctly, your app might -

• Fail to initialize tracking as expected

• Send incomplete hits

• Or route data to an unintended fallback suite
  
  

A quick way to confirm: try opening the Production config file URL in a browser or proxy tool to make sure it actually returns something meaningful. If it's empty or broken, that’s likely the root cause.

My suggestion: publish at least a basic version of the tag to Production first (even with just one rule), that way, the SDK gets a valid config, and you'll have better visibility into how data is flowing.

Hope that helps!

[Jennifer_Dungan · Accepted solution]

Hmm I've never seen anything like that "Development" show up like that before... Given there are other elements to the page missing, I am assuming that maybe you only have read-only access as apposed to full access... but I wonder if that is not the "published status" (since that shouldn't appear at all like that), but rather this is the prod/sandbox partition...

https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/home 

We only have a Prod partition... but IF this is a development partition, even if it's "fully deployed", it might not be sending data to your production suite because it's virtualized... I'm not sure... 

The only place to see the published status of a Property is in the Publishing Flow area of Launch...  There is nothing at all in or near the title of the property with any indication of the status...