-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updating Webhook example, verbiage per legal, and punctionation
- Loading branch information
1 parent
9f4e6cd
commit 2bf3022
Showing
8 changed files
with
81 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,13 +6,13 @@ section_title: App Marketplace | |
--- | ||
|
||
## Introduction | ||
Partner integrations empower our mutual customers, driving further adoption. By leveraging our co-marketing opportunities, you can both promote your app and strengthen its integration within the Procore ecosystem, reaching more customers and demonstrating its value. | ||
Partner integrations empower our mutual customers, driving further adoption. By leveraging our self-service marketing opportunities, you can both promote your app and strengthen its integration within the Procore ecosystem, allowing you to reach more customers and demonstrate its value. | ||
|
||
We’ve designed these opportunities to help you maximize the impact of your apps and integrations built on our API, while streamlining the co-marketing process for self-service. | ||
<br><br> | ||
|
||
*** | ||
## Co-Marketing Opportunities | ||
## Marketing Opportunities | ||
There are two main channels when it comes to co-marketing opportunities with Procore, Press Releases and Social Media & Blog Posts. To understand more about each one, and the items that it supports, review the content below. | ||
|
||
|
||
|
@@ -35,27 +35,27 @@ There are two main channels when it comes to co-marketing opportunities with Pro | |
|
||
- **New Content or News Feature:** Share newly published articles, blogs, or news featuring your partnership with Procore. Focus on highlighting key themes, insights, or benefits that resonate with the construction industry. Use this opportunity to underscore how your collaboration with Procore helps users achieve their goals. | ||
|
||
To participate in any of these co-marketing activities, refer to the **Review Process** section of this guide to understand how, and when, to submit public facing materials mentioning Procore. | ||
To participate in any of these marketing activities, refer to the **Review Process** section of this guide to understand how, and when, to submit public facing materials mentioning Procore. | ||
<br><br> | ||
<!-- Additionally, refer to our Press Release and Best Practices for Blogs and Social Media Posts to prevent delays or rejections. --> | ||
|
||
*** | ||
## Co-Marketing Guidelines | ||
## Marketing Guidelines | ||
As detailed in the <a href="https://www.procore.com/partners/documents" target="blank">Procore Partner Agreement</a>, Partners are responsible for accurately representing Procore and the partnership in all public facing materials produced by the Partner, including but not limited to press releases, social media copy, blogs, and webinar content. This includes ensuring compliance with the <a href="https://brand.procore.com/design/logos/?_gl=1*13n0feh*_gcl_au*Mjk3NzY4NjQxLjE3Mjg1MTUwNzY.*_ga*NTEyMTM3NDQ1LjE3MjM4MzU1NDk.*_ga_DDN1X7BZGJ*MTcyODg1NjMxNi42LjEuMTcyODg1Nzk3NS45LjAuMA..*_ga_0W3CW2NEWP*MTcyODg1NjMxNi4xMC4xLjE3Mjg4NTc5NzUuOS4wLjA.#overview" target="blank">Brand Use Guidelines</a>, <a href="https://www.procore.com/legal/trademark#otnotice-section-785579e4-abc0-4846-850b-cfb5bf95ab45" target="blank">Trademark Use Guidelines</a>, as well as the additional guidelines outlined below. | ||
|
||
### Review Process | ||
Partners are required to submit any public facing materials mentioning Procore for review to the Partner Programs & Experience team at <[email protected]>. Please include your desired launch timing for all public facing marketing collateral. Procore will aim to provide a response within 5 business days. Once approved, you are responsible for the logistics and costs of distribution, and announcement timing must be conducted in the approved window provided by Procore. | ||
Partners are required to submit any public facing materials mentioning Procore for review to the Partner Programs & Experience team at <[email protected]>. Please include your desired launch timing for all public facing marketing collateral. Procore will aim to provide a response within 7-10 business days. Once approved, you are responsible for the logistics and costs of distribution, and announcement timing must be conducted in the approved window provided by Procore. | ||
|
||
Please note that Procore does not make public announcements during its quarterly quiet periods, which typically take place two weeks prior to our quarterly earnings announcements. All requests for external communications during these timeframes will be delayed until the conclusion of the corresponding quiet period. | ||
Please note that Procore does not make public announcements during its quarterly quiet periods, which typically take place two weeks prior to our quarterly earnings announcements or during the quiet period around Groundbreak, Procore’s annual construction innovation event. All requests for external communications during these timeframes will be delayed until the conclusion of the corresponding quiet period. | ||
|
||
### Enforcement Actions | ||
Partners that do not comply with Procore’s <a href="https://brand.procore.com/design/logos/?_gl=1*13n0feh*_gcl_au*Mjk3NzY4NjQxLjE3Mjg1MTUwNzY.*_ga*NTEyMTM3NDQ1LjE3MjM4MzU1NDk.*_ga_DDN1X7BZGJ*MTcyODg1NjMxNi42LjEuMTcyODg1Nzk3NS45LjAuMA..*_ga_0W3CW2NEWP*MTcyODg1NjMxNi4xMC4xLjE3Mjg4NTc5NzUuOS4wLjA.#overview" target="blank">Brand Use Guidelines</a> and/or <a href="https://www.procore.com/legal/trademark#otnotice-section-785579e4-abc0-4846-850b-cfb5bf95ab45" target="_blank">Trademark Usage Guidelines</a> will be subject to a partnership review and possible change in program benefits, including loss of status as a Procore Partner, per the Partner Agreement. | ||
Partners that do not comply with Procore’s <a href="https://brand.procore.com/design/logos/?_gl=1*13n0feh*_gcl_au*Mjk3NzY4NjQxLjE3Mjg1MTUwNzY.*_ga*NTEyMTM3NDQ1LjE3MjM4MzU1NDk.*_ga_DDN1X7BZGJ*MTcyODg1NjMxNi42LjEuMTcyODg1Nzk3NS45LjAuMA..*_ga_0W3CW2NEWP*MTcyODg1NjMxNi4xMC4xLjE3Mjg4NTc5NzUuOS4wLjA.#overview" target="blank">Brand Use Guidelines</a>, <a href="https://www.procore.com/legal/trademark#otnotice-section-785579e4-abc0-4846-850b-cfb5bf95ab45" target="_blank">Trademark Usage Guidelines</a>, and other applicable policies will be subject to a partnership review and possible change in program benefits, including loss of status as a Procore Partner, per the Partner Agreement. | ||
|
||
Actions taken may include, without limitation, declining all citation requests from companies with active citation violations as well as cease and desist orders to remove content. If you have questions about what constitutes a violation, or you believe that you have found a violation, please contact us at <[email protected]>. | ||
Actions taken may include, without limitation, declining all citation requests from companies with active citation violations as well as demands to remove content. If you have questions about what constitutes a violation, or you believe that you have found a violation, please contact us at <[email protected]>. | ||
<br><br> | ||
|
||
*** | ||
## Co-Marketing Resources | ||
## Marketing Resources | ||
To help you get started, we’ve made several resources available to your marketing team, including: | ||
|
||
<ul> | ||
|
@@ -73,6 +73,6 @@ We encourage you to use these resources to create co-branded content that aligns | |
*** | ||
### Updates to Guidelines and Enforcement | ||
|
||
Procore Technologies reserves the right to revise the Developer Documentation in its discretion. | ||
Procore Technologies reserves the right to revise the Developer Documentation at any time, in its sole discretion. | ||
|
||
As described in the applicable terms and conditions, Procore may remove or decline the publication of any application listing or co-marketing opportunity at any time. | ||
As described in the applicable terms and conditions, Procore may remove or decline the publication of any Marketplace Listing or co-marketing opportunity at any time. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,7 +9,7 @@ section_title: App Marketplace | |
## Introduction | ||
Before submitting your app for approval, it’s essential to review this Marketplace Approval Checklist. This checklist outlines submission requirements, helping ensure your app aligns with our guidelines for a seamless review process. | ||
|
||
By following this checklist, you'll ensure your app meets Procore’s high standards, minimizing delays and positioning your app for success in the Marketplace. | ||
Following this checklist helps ensure your app meets Procore’s high standards, minimizing delays and positioning your app for success in the Marketplace. | ||
<br><br> | ||
|
||
*** | ||
|
@@ -21,17 +21,17 @@ Ensure the following steps are completed before submitting your app to avoid rej | |
<details> | ||
<summary class="collapseListTierOne">1. You Are a Procore Partner</summary> | ||
<p> | ||
Approved Procore Partners receive a signed Partner Framework Agreement via email upon successful completion of the contracting process. This marks the final step and confirms your status as a Procore Partner. | ||
Approved Procore Partners receive a signed Partner Framework Agreement and Technology Partner Addendum via email upon successful completion of the contracting process. This marks the final step and confirms your status as a Procore Partner. | ||
<br><br> | ||
If you're unsure about your partner status, contact <a href= "mailto: [email protected]"> [email protected]</a>. You can also apply to become a Procore Partner directly in the <b>Marketplace Listing</b> section of your app. | ||
If you're unsure about your partner status, contact <a href= "mailto: [email protected]"> [email protected]</a>. You can also apply to become a Procore Partner directly in the <b>Marketplace Listing</b> section of your app, through the Developer Portal. | ||
</p> | ||
</details> | ||
|
||
*** | ||
<details> | ||
<summary class="collapseListTierOne">2. You Have an Active Customer Using the App</summary> | ||
<p> | ||
Prior to having your app approved, and ultimately published to the Procore Marketplace, your app must have at least one (1) beta customer as described in the <a href="https://www.procore.com/partners/documents" target="_blank">Partner Program Guide</a>. This beta customer should help provide feedback about onboarding and functionality before your app being submitted for review. | ||
Prior to having your app approved, and ultimately published to the Procore Marketplace, your app must have at least one (1) beta customer as described in the <a href="https://www.procore.com/partners/documents" target="_blank">Partner Program Guide</a>. This beta customer should help provide feedback about onboarding and functionality before submitting your app for review. | ||
<br><br> | ||
This step builds confidence among prospective users, as customers often hesitate to adopt a new solution without prior customer usage. | ||
</p> | ||
|
@@ -41,10 +41,10 @@ Ensure the following steps are completed before submitting your app to avoid rej | |
<details> | ||
<summary class="collapseListTierOne">3. Your App Has Been Thoroughly Tested</summary> | ||
<p> | ||
As described in <a href="{{ site.url }}{{ site.baseurl }}{% link app_marketplace/marketplace_requirements.md %}">Getting Started & Requirements</a>, the Procore Marketplace is not meant for beta or trial apps. Prior to having your app be published, you must thoroughly tested the following items: | ||
As described in <a href="{{ site.url }}{{ site.baseurl }}{% link app_marketplace/marketplace_requirements.md %}">Getting Started & Requirements</a>, the Procore Marketplace is not meant for beta or trial apps. Prior to having your app be published, you must thoroughly test the following items: | ||
</p> | ||
<ul> | ||
<li>The app installation and configuration processes (both in your service and Procore).</li> | ||
<li>The app installation and configuration processes (both in your/third party service and Procore).</li> | ||
<li>The customer onboarding experience.</li> | ||
<li>The usage of all the app features.</li> | ||
<li>If necessary, your app supports Procore's multi-company architecture.</li> | ||
|
@@ -66,7 +66,7 @@ Additionally, take into consideration how your app will handle rate limiting and | |
<li>Any specific requirements for customers.</li> | ||
</ul> | ||
<p> | ||
If your listing is not enabled, request to have it activated through the <b>Marketplace Listing</b> tab in your app. For field requirements, see <a href="{{ site.url }}{{ site.baseurl }}{% link app_marketplace/marketplace_listing_guidelines.md %}">Marketing Listing Guidelines</a>. | ||
If your listing is not enabled, request to have it activated through the <b>Marketplace Listing</b> tab in your app, accessible via the Developer Portal. For field requirements, see <a href="{{ site.url }}{{ site.baseurl }}{% link app_marketplace/marketplace_listing_guidelines.md %}">Marketing Listing Guidelines</a>. | ||
</p> | ||
</details> | ||
|
||
|
@@ -77,13 +77,13 @@ Additionally, take into consideration how your app will handle rate limiting and | |
When submitting your app for initial approval or when updating functionality, provide a 3-5 minute long demo video in the <b>Admin App Specifications</b> section of the Marketplace Listing that showcases the following: | ||
</p> | ||
<ul> | ||
<li>App installation and configuration processes (both in your service and Procore).</li> | ||
<li>Steps to link Procore accounts to your external service (e.g., selecting a Procore company).</li> | ||
<li>App installation and configuration processes (both in your service/third party service and Procore).</li> | ||
<li>Steps to link Procore accounts to the external service (e.g., selecting a Procore company).</li> | ||
<li>End-to-end app functionality, including data creation or visualization within Procore.</li> | ||
<li>User experience for embedded apps (if applicable).</li> | ||
</ul> | ||
<p> | ||
For non-functional updates to the listing, you may reuse the original video. | ||
For non-functional updates to the Marketplace Listing, you may reuse the original video. | ||
</p> | ||
</details> | ||
|
||
|
@@ -93,21 +93,21 @@ Additionally, take into consideration how your app will handle rate limiting and | |
<p> | ||
While you can always update your Marketplace Listing at any time, ensure links, descriptions, functionality, and permissions are correctly reflected and are not misleading when submitting your app for approval. | ||
<br><br> | ||
Clearly convey the value of your app and how it will help the end-user, whether it's increasing operational efficiency or providing data accuracy. The customer wants to know <i>how</i> this integration is valuable to them and <i>why</i> they should adopt your solution. If possible, support a free trial to help engage the customer and provide them with direct steps to get started. | ||
Clearly convey the value of your app and how it will help the customer, whether it's increasing operational efficiency or providing data accuracy. The customer wants to know <i>how</i> this integration is valuable to them and <i>why</i> they should adopt your app. If possible, support a free trial to help engage the customer and provide them with direct steps to get started. | ||
</p> | ||
</details> | ||
|
||
*** | ||
<details> | ||
<summary class="collapseListTierOne">7. You Are Supporting The Production Environment</summary> | ||
<p> | ||
After testing in the Developer Sandbox, ensure your app is production-ready by updating specific items in the Procore Developer Portal or in your source code. Since each app is unique, this process can vary from app-to-app. | ||
After testing in the Developer Sandbox, ensure your app is production-ready by updating specific items in the Procore Developer Portal or in your source code. This process can vary since each app is unique. | ||
</p> | ||
<div> | ||
<h4>General Steps</h4> | ||
<ul> | ||
<li>Customize the 'Post Installation Notes’ in the <b>Configuration Builder</b> section of your app to clearly explain how the app is configured within your service, and if applicable, in Procore.</li> | ||
<li>Promote your app to production inside your app, through the <a href="https://developers.procore.com/developers" target="_blank">Procore Developer Portal</a>.</li> | ||
<li>Customize the 'Post Installation Notes’ in the <b>Configuration Builder</b> section of your app to clearly explain how the app is configured within your service/third party service, and if applicable, in Procore.</li> | ||
<li>Through the <a href="https://developers.procore.com/developers" target="_blank">Procore Developer Portal</a>, promote your app to production.</li> | ||
</ul> | ||
</div> | ||
<div> | ||
|
@@ -122,7 +122,7 @@ After testing in the Developer Sandbox, ensure your app is production-ready by u | |
<li>Update Base URLs for token management to <code>https://login.procore.com</code>.</li> | ||
<li>Update Base URLs for API calls to <code>https://api.procore.com</code>.</li> | ||
<li>Update your source code with the production Client ID and Secret provided to you within your app.</li> | ||
<li>If using User Level Authentication, update the base URL and Client ID for your callback URL, which is used to generate access token.</li> | ||
<li>If using User Level Authentication, update the base URL and Client ID for your callback URL, which is used to generate the access token.</li> | ||
<li>Pass the Procore Company ID in API headers for all calls except:</li> | ||
<ul> | ||
<li>Token management (generate, refresh, revoke).</li> | ||
|
@@ -131,7 +131,7 @@ After testing in the Developer Sandbox, ensure your app is production-ready by u | |
</ul> | ||
<li>For Service Account Authentication, adhere to the principle of least privileged permissions. For example:</li> | ||
<ul> | ||
<li>If your app does not interact with the Directory tool, then it should not have permissions to Directory.</li> | ||
<li>If your app does not interact with the Directory tool, then it should not have permissions to the Directory.</li> | ||
<li>If your app is reading information from Procore, it should not have Admin access to the specific solution.</li> | ||
</ul> | ||
</ul> | ||
|
@@ -142,15 +142,15 @@ After testing in the Developer Sandbox, ensure your app is production-ready by u | |
<div class="bulletedBreak"></div> | ||
|
||
## How to Submit Your App For Review | ||
Submit your app through the **Marketplace Listing** section of your app, within the <a href="https://developers.procore.com/developers" target="_blank">Developer Portal</a>. If the listing section is not enabled, request activation within your app or confirm your Procore Partner status. | ||
Submit your app through the **Marketplace Listing** section of your app, within the <a href="https://developers.procore.com/developers" target="_blank">Developer Portal</a>. If the listing section is not enabled, request activation within your app and confirm your Procore Partner status. | ||
|
||
The Marketplace Team will review your submission to ensure all [Marketplace Requirements]({{ site.url }}{{ site.baseurl }}{% link app_marketplace/marketplace_requirements.md %}) are met. | ||
<br><br> | ||
|
||
*** | ||
## Additional Considerations | ||
### Provide Support Documentation | ||
To maintain a high level of customer satisfaction, your support system must be ready to assist users. Procore’s support team does not troubleshoot technical issues with your app, so you should establish a support system with: | ||
To maintain a high level of customer satisfaction, your support system must be ready to assist users. Procore’s support team does not troubleshoot technical issues with your app, so you should establish a support system with at a minimum: | ||
|
||
- Up-to-date support content, kept current with changes to the app. | ||
- A publicly accessible URL for your support documentation. | ||
|
@@ -171,6 +171,6 @@ For more details about the Monthly Sandbox, including the refresh schedule and a | |
|
||
*** | ||
### Updates to Guidelines and Enforcement | ||
Procore Technologies reserves the right to revise the Developer Documentation in its discretion. | ||
Procore Technologies reserves the right to revise the Developer Documentation at any time, in its sole discretion. | ||
|
||
As described in the applicable terms and conditions, Procore may remove or decline the publication of any application listing at any time. | ||
As described in the applicable terms and conditions, Procore may remove or decline the publication of any Marketplace Listing at any time. |
Oops, something went wrong.