# Can custom parameters (ulp-xxx) be used with ACUL's social sign-up (federatedSignup())?

**URL:** <https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [September 17, 2026, 2:59pm UTC](https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432 "2026-09-17T14:59:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![takaya.otsu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/takaya.otsu/32/80840_2.png) [@takaya.otsu](https://community.auth0.com/u/takaya.otsu)\
**Post date:** [September 17, 2026, 2:59pm UTC](https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432/1 "2026-09-17T14:59:23Z")

</div>

I’d like to ask whether custom parameters (`ulp-xxx`) can be used with ACUL’s social sign-up (`federatedSignup()`).

**[Current understanding]**

- With `federatedLogin()`, custom parameters (`ulp-xxx`) can be used.  
Reference: [Login - Auth0 Docs](https://auth0.com/docs/libraries/acul/react-sdk/API-Reference/Screens/login#param-federated-login)

- On the other hand, with `federatedSignup()`, custom parameters (`ulp-xxx`) cannot be used (as described below, I actually verified this, and `ulp-xxx` could not be referenced in Post Login Actions).  
Reference: [Signup - Auth0 Docs](https://auth0.com/docs/libraries/acul/react-sdk/API-Reference/Screens/signup#param-federated-signup)

- Although not ACUL, Universal Login’s custom prompts can be used (even for social sign-up).  
Reference: [Auth0 Changelog](https://auth0.com/changelog#3MmWnmhpwRradIv0TpieUW)  
_Note: this was changed in the August changelog._

* * *

**[Question]**

As described above, it appears that `federatedSignup()` is the only case where custom parameters cannot be used.

1. Is this an intentional design/specification? Or is there an issue with how I verified it (i.e., can custom parameters actually be used)?
2. If it is by design, is there a workaround? (For example, is it possible to invoke processing equivalent to `federatedLogin()`?)
3. If there is no such workaround, are there any plans to support this in the future?

* * *

**[Verification details]**

I verified this as follows.

- Environment
  - Free tenant (with a custom domain configured)
  - ACUL: `@auth0/auth0-acul-react` (customizing the signup-id / login-id screens)

- Verification method
  - On the signup-id screen, executed sign-up via a social connection using `federatedSignup({ connection, 'ulp-consented_at': <ISO timestamp> })`
  - On the login-id screen, executed login via a social connection using `federatedLogin({ connection, 'ulp-consented_at': <ISO timestamp> })`
  - On the Post-Login Action side, checked the contents of `event.request.query` / `event.request.body` / `event.transaction`
  - _Result: `ulp-consented_at` did not arrive in the sign-up case, but did arrive in the login case._

* * *

@michael.swanson  
Apologies for the mention.  
I saw a reference to a similar issue in the following topic, so I’d appreciate any advice if you happen to know anything about this.  
[https://community.auth0.com/t/acul-sending-custom-data-on-signup/184130/5](https://community.auth0.com/t/acul-sending-custom-data-on-signup/184130/5)

Thank you in advance.

================================  
Japanese version below / 日本語版は以下をご覧ください

タイトル：ACULのソーシャルサインアップ（federatedSignup()）において、カスタムパラメータ（ `ulp-xxx` ）が使えるか？

ACULのソーシャルサインアップ（federatedSignup()）において、カスタムパラメータ（ `ulp-xxx` ）が使えるか？を質問させてください。

【現状の理解】

- federatedLogin()では、カスタムパラメータ（ `ulp-xxx` ）が利用できる  
参考：[Login - Auth0 Docs](https://auth0.com/docs/libraries/acul/react-sdk/API-Reference/Screens/login#param-federated-login)

- 一方で、federatedSignup()では、カスタムパラメータ（ `ulp-xxx` ）が利用できない（後述の通り、実際に検証したが、`ulp-xxx`はPost Login Actionsで参照できなかった）  
参考：[Signup - Auth0 Docs](https://auth0.com/docs/libraries/acul/react-sdk/API-Reference/Screens/signup#param-federated-signup)

- ACULではないが、Universal Loginのカスタムプロンプトが（ソーシャルサインアップでも）使える  
参考：[Auth0 Changelog](https://auth0.com/changelog#3MmWnmhpwRradIv0TpieUW)  
※8月のChangeLogで変更されている

* * *

【質問】  
上記の通り、federatedSignup()のみカスタムパラメータが使えないように見えるが、

①これは意図的な仕様なのか？もしくは、検証の仕方が悪いのか（実際にはカスタムパラメータが使えるのか）？  
②仕様の場合、回避策はあるか？（例えば、federatedLogin()と同等の処理を呼び出せる？）  
③上記回避策もない場合、将来対応予定はあるか？

* * *

【検証内容】  
以下の通り、検証しました。

- 環境
  - 無料テナント（カスタムドメイン設定済み）
  - ACUL：@auth0/auth0-acul-react（signup-id / login-id 画面をカスタマイズ）

- 検証方法
  - signup-id 画面の federatedSignup({ connection, ‘ulp-consented\_at’: \<ISO日時\> }) で social  
接続 経由のサインアップを実行
  - login-id 画面の federatedLogin({ connection, ‘ulp-consented\_at’: \<ISO日時\> }) で social 接続 経由のログインを実行
  - Post-Login Action 側で event.request.query / event.request.body / event.transaction の中身を確認
  - ※signupではulp-consented\_atは届かず、loginでは届いた

* * *

@michael.swanson  
メンション失礼します。  
以下のトピックで、似た件への言及がありましたので、何かご存じでしたらアドバイスいただければ嬉しいです。  
[https://community.auth0.com/t/acul-sending-custom-data-on-signup/184130/5](https://community.auth0.com/t/acul-sending-custom-data-on-signup/184130/5)

よろしくお願いいたします。

#new-universal-login-experience #login-experience

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [September 18, 2026, 3:22pm UTC](https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432/3 "2026-09-18T15:22:36Z")

</div>

Hi @takaya.otsu

Welcome to the Auth0 Community!

You are asking whether custom parameters (`ulp-xxx`) can be used with Auth0's Adaptive Consent User Login (ACUL) SDK's `federatedSignup()` method for social sign-up flows. You have verified that custom parameters work with `federatedLogin()` but do not arrive in Post-Login Actions when using `federatedSignup()`, even though the documentation does not explicitly state this limitation. You want to know whether this is intentional, whether there is a workaround, or whether Auth0 plans to support this in the future.

**This appears to be an undocumented limitation or potential bug in the ACUL SDK. Your verification is correct and thorough. Auth0 Support needs to clarify whether this is intentional design or a bug, and provide guidance on workarounds or timelines for resolution.**

**Root Cause:**

The discrepancy between `federatedLogin()` and `federatedSignup()` regarding custom parameter support suggests one of these causes:

1. **Intentional design limitation** — `federatedSignup()` may be designed to exclude custom parameters for security or UX reasons
2. **Bug in the ACUL SDK** — Custom parameters may be intended to work but are not being passed through correctly in the signup flow
3. **Documentation gap** — The behavior may be intentional but not documented, leaving developers unaware of the limitation
4. **Incomplete implementation** — The feature may have been added to `federatedLogin()` but not yet implemented for `federatedSignup()`

**Your Verification Is Correct:**

Your testing approach is sound:

- **Testing method:** Using `federatedSignup()` and `federatedLogin()` with identical custom parameters and checking Post-Login Actions is the correct way to verify parameter passing
- **Verification points:** Checking `event.request.query`, `event.request.body`, and `event.transaction` covers all the places where parameters should arrive
- **Result:** The parameter arrived in the login case but not in the signup case, confirming a real discrepancy

**Recommended Next Steps:**

**1. Contact Auth0 Support directly**

**Create a support ticket with:**

- **Your tenant domain** (e.g., `dev-xxxxx.us.auth0.com`)
- **Your ACUL SDK version** (e.g., `@auth0/auth0-acul-react@x.x.x`)
- **Exact code used for both flows:**

```
// Signup flow
federatedSignup({ connection: 'google-oauth2', 'ulp-consented_at': '<ISO timestamp>' })

```

- **Post-Login Action code** that checks for the parameter: 

```
exports.onExecutePostLogin = async (event, api) => {
  console.log('Query:', event.request.query);
  console.log('Body:', event.request.body);
  console.log('Transaction:', event.transaction);
};
```

- **Screenshots or logs** showing: 
  - Parameter arriving in login case
  - Parameter NOT arriving in signup case

- **Question:** Is this an intentional limitation, a bug, or a documentation gap?

**2. Check the ACUL SDK documentation and changelog**

**Review:**

- The official ACUL SDK documentation for `federatedSignup()` to see if custom parameters are mentioned as unsupported
- The Auth0 changelog to see if there are any recent updates or known issues related to `federatedSignup()` and custom parameters
- GitHub issues in the auth0-acul-react repository for similar reports

**3. Explore potential workarounds**

**If Auth0 confirms this is intentional, consider:**

- **Using `federatedLogin()` instead** — If your use case allows, use `federatedLogin()` for both first-time and returning users (social connections treat first login as signup)
- **Passing parameters via state** — Use the `state` parameter to pass custom data, though this is less secure and intended for CSRF prevention
- **Post-login parameter injection** — Use a Post-Login Action to set user metadata based on other signals (e.g., `event.stats.logins_count === 1` to detect first login)
- **Custom prompts** — Use Auth0's custom prompts feature to collect additional data after signup completes

**4. Request a feature enhancement**

**If Auth0 confirms this is a limitation, submit a feature request:**

- **Visit** the Auth0 feedback page
- **Request:** Support for custom parameters in `federatedSignup()`
- **Justification:** Parity with `federatedLogin()` and the ability to pass context-specific data during social signup flows
- **Use case:** Tracking consent timestamps, signup source, or other metadata during federated signup

**Why This Requires Auth0 Support:**

- **ACUL is a managed SDK** — Only Auth0 engineers can confirm whether this is by design or a bug
- **SDK-level behavior** — This is not a configuration issue; it's a question about how the SDK processes parameters
- **Potential bug** — If this is unintentional, it should be reported to the Auth0 engineering team for a fix
- **Documentation gap** — If intentional, the documentation should be updated to clarify this limitation

Additionally, you can attempt to [pass the custom parameter inside a Pre-User Registration Trigger](https://support.auth0.com/center/s/article/passing-custom-parameters-to-pre-user-registration-actions):

### Prerequisites

Custom Domain: This solution relies on Page Templates/Partials, which require a Custom Domain to be configured.

Database Connections Only: This solution works exclusively with Auth0 Database connections during the signup flow.

The tenant must be using Universal Login, and the “Customise Login Page” toggle (Classic Login) must be disabled.

### Pass the parameter from the application

1. Locate the login method call within the application code.
2. Append the custom parameter to the `authorizationParams` object.
3. Prefix the parameter name with `ext-`.

```auto
// Example using the Auth0 Angular SDK
this.auth.loginWithPopup({
  authorizationParams: {
  'ext-my_custom_param': 'your_custom_value' // The param to save
  }
});

```

### Update the Signup Prompt via Partials

Inject the parameter into the HyperText Markup Language (HTML) payload of the signup form.

NOTE: Auth0 strips out standard `<input type="hidden">` elements. To bypass this, use a standard text input but hide it using inline CSS (`type="text" style="display: none;"`).

```auto
<input 
  type="text" 
  style="display: none;" 
  name="ulp-my_custom_param" 
  value="{{ transaction.params['ext-my_custom_param'] | escape }}" 
/>

```

#### **Option A: Identifier First Login**

If the tenant requests the email first and the password on a separate screen, update the signup-id prompt:

```auto
curl --request PUT \
  --url 'https://[TENANT-NAME].[REGION].auth0.com/api/v2/prompts/signup-id/partials' \
  --header 'Authorization: Bearer YOUR_MANAGEMENT_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "signup-id": {
      "form-content-end": "<input type=\"text\" style=\"display: none;\" name=\"ulp-my_custom_param\" value=\"{{ transaction.params['\''ext-my_custom_param'\''] | escape }}\" />"
    }
  }'

```

#### 

#### **Option B: Identifier + Password Login (Standard)**

If the tenant asks for both the Email and Password on the exact same screen, update the standard `signup` prompt:

```auto
curl --request PUT \
  --url 'https://[TENANT-NAME].[REGION].auth0.com/api/v2/prompts/signup/partials' \
  --header 'Authorization: Bearer YOUR_MANAGEMENT_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "signup": {
      "form-content-end": "<input type=\"text\" style=\"display: none;\" name=\"ulp-my_custom_param\" value=\"{{ transaction.params['\''ext-my_custom_param'\''] | escape }}\" />"
    }
  }'

```

### Access the parameter in the Action

1. In the Pre-User Registration Action, retrieve the custom parameter from the `event.request.body` object.
2. Save the value to the user metadata.

```auto
exports.onExecutePreUserRegistration = async (event, api) => {

  // 1. Grab the value from the form submission payload
  const myCustomParam = event.request.body['ulp-my_custom_param'];

  // 2. Validate and write to app_metadata (or user_metadata)
  if (myCustomParam) {
    //api.user.setAppMetadata("my_custom_param", myCustomParam);
    api.user.setUserMetadata("my_custom_param", myCustomParam);
  }
};

```

### Warning

- Query parameters can be easily manipulated by an end-user in their browser’s address bar.
- _P_erform backend validation inside the Action if the parameter is sensitive (for example, a “beta invite code” or “role ID”), the Action must validate it against an external API or signature before trusting it and saving it to `metadata`.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![takaya.otsu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/takaya.otsu/32/80840_2.png) [@takaya.otsu](https://community.auth0.com/u/takaya.otsu)\
**Post date:** [September 25, 2026, 4:25am UTC](https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432/4 "2026-09-25T04:25:13Z")

</div>

**Update:**

After re-verifying, I’ve confirmed that with both `federatedSignup()` / `federatedLogin()`, custom parameters with the `ulp-` prefix correctly arrive in `event.request.body` in Post Login Actions during social sign-up/login as well.

(In my previous verification, the parameter did not arrive on the signup side, but based on this re-check it now arrives correctly. This may have been due to some difference in the environment at the time.)

I’m sharing this in case it helps others facing the same issue.

Also, we have our own custom Action (involving Account Linking and redirect-based processing), and we found that this can cause the custom parameters to be lost. I haven’t strictly isolated exactly which part of the processing causes this, but when I temporarily removed that Action and re-verified, the custom parameters were received correctly. If you have a similar custom Action implemented, please be aware of this as a precaution.

================================  
Japanese version below / 日本語版は以下をご覧ください

追記です。

改めて検証したところ、federatedSignup() / federatedLogin() 経由のソーシャルサインアップ・ログインいずれにおいても、  
ulp-プレフィックス付きのカスタムパラメータが Post Login Actions の event.request.body まで正しく届くことを確認できました。

（前回の検証時は signup 側で届かない結果になっていましたが、今回改めて確認した限りでは正しく届いています。環境差分等が原因だった可能性があります。）

同じ点で悩んでいる方の参考になればと思い共有します。

なお、弊社では独自のAction（Account Linkingやリダイレクトを伴う処理）を実装しており、これが原因でカスタムパラメータが失われるケースがあることも分かりました。  
どの処理が具体的に影響しているかまでは厳密に切り分けられていませんが、当該処理を一時的に外した状態で再検証したところ、カスタムパラメータを正常に受信できることを確認しました。  
類似のActionを実装されている方は、念のためご注意ください。

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [October 5, 2026, 4:26am UTC](https://community.auth0.com/t/can-custom-parameters-ulp-xxx-be-used-with-aculs-social-sign-up-federatedsignup/203432/5 "2026-10-05T04:26:00Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
