Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Visualforce Interactions

Each record in your package usage log that has a custom_entity_type of VisualforcePage describes an interaction with your packaged Visualforce pages.

Available in: both Salesforce Classic and Lightning Experience

Available in: Enterprise, Performance, Unlimited, and Developer Editions

Visualforce Requests

When a user performs an action that results in a request associated with your VisualForce page, log_record_type equals VisualforceRequest. One standard field is always populated with data: url.

Visualforce page requests also have supplemental fields that are often populated. For example, a Visualforce page request sometimes also has request_status and referrer_uri data.

Use these fields to explore the details of the Visualforce request.

Standard Data	Supplemental Data
`url`	`request_status` `referrer_uri` `request_status` `response_size`

Example

Let’s look at an example package usage log record and analyze the Visualforce request.

1{
2     "timestamp_derived": "2022-11-22T06:23:23.836Z",
3     "log_record_type": "VisualforceRequest",
4     "request_id": "4mbi9e1ZVef83tlq2Z5aAk",
5     "organization_id": "00Dxx0000006H2l",
6     "organization_name": "MyCustomer Inc.",
7     "organization_status": "Demo",
8     "organization_edition": "Enterprise Edition",
9     "organization_country_code": "IN",
10     "organization_language_locale": "en_US",
11     "organization_time_zone": "Australia/Sydney",
12     "organization_instance": "GS0",
13     "organization_type": "Production",
14     "user_id_token": "005-9BwnBWYO5FMn4cZ1sLw7F3LmTpoe8M77GrZOZHL6xQk=",
15     "user_type": "Standard",
16     "url": "/apex/Acme__Agent_List",
17     "package_id": "033xx0000004FqD",
18     "package_version_id": "04txx0000004Idi",
19     "managed_package_namespace": "Acme",
20     "custom_entity": "/apex/Acme__Agent_List",
21     "custom_entity_type": "VisualforcePage",
22     "request_status": "S",
23     "session_key": "2l4YtFB/RmsRKVsS",
24     "login_key": "fGV6RgVOH3ZCgl2v",
25     "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/IP_ADDRESS_REMOVED Safari/537.36",
26     "user_country_code": "US",
27     "user_time_zone": "America/Los_Angeles",
28     "request_size": "826",
29     "response_size": "1830"
30}

The Acme_Agent_List packaged component of type VisualforcePage was interacted with as a result of a user action from subscriber org MyCustomer Inc on 2022-11-22 at 6:23 am.

The key data in this analysis are:

Question	Field	Value
What	`custom_entity` `custom_entity_type` `package_version_id` `managed_package_namespace`	`Acme__Agent_List` `VisualforcePage` `04txx0000004Idi` `Acme`
Who	`organization_id` `user_id_token`	`00Dxx0000006H2l` `005-9BwnBWYO5FMn4cZ1sLw7F3LmTpoe8M77GrZOZHL6xQk=`
How	`log_record_type`	`VisualforceRequest`
When	`timestamp_derived`	`2022-11-22T06:23:23.836Z`

Second-Generation Managed Packaging Developer Guide

Visualforce Interactions

Visualforce Requests

Example

See Also